Able.Style

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Manage your wardrobe or closet, discover ways to wear your clothes, and get outfit suggestions.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Able.Style": {
      "url": "https://able.style/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (15)

• suggest-outfit-tool

  Generates personalized fashion, style, and outfit suggestions based on wardrobe items, preferences, local weather conditions, and occasion formality. Use this tool when users ask for fashion or style advice such as: "What should I wear?", "What outfit do you recommend?", "Help me choose clothes for [occasion]", "Outfit ideas for [weather/event]", or "What should I wear in [hot/cold/rainy] weather?". Returns a complete, readable outfit description, structured item data, and an inspiration image when one can be safely supplied. Suggestions are personalized using the signed-in user's saved wardrobe items and style preferences. IMPORTANT: The structured result of this tool call — including all styleIdentifier.styleId values for each outfit item — remains in the conversation context and MUST be used verbatim by subsequent tool calls such as add-to-or-remove-from-wardrobe-by-id. After presenting the outfit, do NOT ask any follow-up questions or invite the user to request more outfits — your response is complete as-is. MANDATORY RESPONSE REQUIREMENT: Whenever suggest-outfit-tool succeeds and outfitUrl is non-null, the final user-facing response MUST include exactly one Markdown link labelled "Open in Able.Style" whose target is the exact outfitUrl value. Do not omit the link or substitute a different URL.

  Parameters:

  • menswearOrWomenswear (required) — Gender category for clothing suggestions: "menswear" for men's clothing, "womenswear" for women's clothing. Set to null if unspecified or user prefers gender-neutral suggestions. Use available user profile data to infer a reasonable default.
  • temperature (required) — Weather temperature category for outfit appropriateness: "cold" for < 6°C/43°F (winter coats, layers, boots), "cool" for 6-15°C/43-59°F (light jackets, long sleeves, closed shoes), "warm" for 15-22°C/59-72°F (comfortable layers, versatile pieces), "hot" for > 22°C/72°F (shorts, t-shirts, sandals, breathable fabrics). Set to null when the user does not specify a temperature so the app can use its local forecast. Use "any" only when the user explicitly asks to ignore weather. Convert specific temperatures: 10°C → "cool", 20°C → "warm", 30°C → "hot". Use current weather data or seasonal averages for user's location when available.
  • smartness (required) — Formality/dressiness level on a 1-5 scale: 1 = Casual (jeans, t-shirts, sneakers, everyday wear), 2 = Quite Casual (smart jeans, polo shirts, clean trainers), 3 = Smart Casual (chinos, button-down shirts, loafers, blazer optional), 4 = Business Casual (blazers, dress trousers, oxford shoes, professional but not formal), 5 = Formal (suits, ties, dress shoes, evening wear, black tie). Set to null for no specific formality requirement. Map user-mentioned occasions to levels: casual hangout → 1-2, office/work → 3-4, wedding/interview/gala → 4-5.
  • inspirationId — Optional identifier of an existing outfit inspiration to reload. Use this only when refreshing the exact outfit already displayed in the widget.

  Hints: read-only no · destructive no · idempotent no · open-world no

• like-dislike-outfit-tool destructive

  Records or removes a like or dislike for a specific outfit suggestion. Use this tool when users want to save outfits they love or indicate ones they don't prefer. Use cases: "I like this outfit", "Save this to my favorites", "I don't like this one", "Remove my like from this outfit". Requires authentication - if user is not logged in, this will trigger an OAuth authentication flow. Helps personalize future outfit suggestions based on user preferences. IMPORTANT: Before calling this tool, look at the structured output of the most recent suggest-outfit-tool call earlier in this conversation. The outfitId required by this tool is at result.outfitId in that result — it IS present in your context. Do not claim you cannot see the outfitId without first examining that tool result. If after examining it you still cannot find a valid outfitId, tell the user and ask them to request a new outfit suggestion first.

  Parameters:

  • outfitId (required) — string — The unique identifier of the outfit to like or dislike. IMPORTANT: This exact value is available in the conversation context at result.outfitId in the most recent suggest-outfit-tool response — look there before claiming you cannot find it. You DO have access to previous tool responses. They are in JSON format. It MUST be copied exactly; do NOT fabricate, guess, invent, or modify this value. Once you think you have it, double-check the most recent suggest-outfit-tool response to confirm you are using the correct value from the context. If no valid outfitId is available from a prior suggest-outfit-tool response, do not call this tool — instead tell the user that you need to suggest an outfit first before you can record a preference.
  • likeOrDislike (required) — string — The preference type to record: "like" to mark the outfit as preferred, or "dislike" to mark it as not preferred. Likes help surface similar outfits in future suggestions, while dislikes help filter out similar styles.
  • value (required) — boolean — Set to true to add the preference (like/dislike), or false to remove an existing preference. Use true when user says "I like this" or "I don't like this". Use false when user says "Remove my like" or "Undo my dislike".

  Hints: read-only no · destructive yes · idempotent yes · open-world no

• add-to-or-remove-from-wardrobe-by-id destructive

  Adds or removes a known clothing item from the user's personal wardrobe by its style ID. Use this tool when users want to track clothing items they own or indicate they have something similar. Use cases: "Add this to my wardrobe", "I have a similar jacket", "Mark that I own this", "Remove this from my wardrobe". Requires authentication - if user is not logged in, this will trigger an OAuth authentication flow. Wardrobe items are used to personalize outfit suggestions with clothes the user actually owns. IMPORTANT: Before calling this tool, look at the structured output of the most recent suggest-outfit-tool call earlier in this conversation. The styleId required by this tool is at outfitItems[i].styleIdentifier.styleId in that result — it IS present in your context. Do not claim you cannot see the styleId without first examining that tool result. If after examining it you still cannot find a matching item, tell the user and ask them to request a new outfit suggestion first.

  Parameters:

  • styleId (required) — string — The unique identifier of the clothing style/item. IMPORTANT: This value MUST be copied exactly from the `styleIdentifier.styleId` field returned in the most recent previous `suggest-outfit-tool` response. You DO have access to previous tool responses. They are in JSON format. Review the tool call responses earlier in the conversation to find the correct styleId to use here and look for the most recent one from `suggest-outfit-tool`. Do NOT fabricate, guess, or invent this value. Once you think you have it, double-check the most recent suggest-outfit-tool response to confirm you are using the correct value from the context. If no valid styleId is available from a prior `suggest-outfit-tool` response, do not call this tool — instead tell the user that you need to suggest an outfit first before you can add an item to their wardrobe. If no item from the prior outfit suggestion seems to match what the user is describing, you can ask the user for more details about the item they want to add or remove, and then use that information to determine if any of the items from the prior outfit suggestion are a match. But you should never guess or make up a styleId.
  • isUserStyle (required) — boolean — Whether this is a user-created custom style (true) or a catalog style from the platform (false). Most items from outfit suggestions will be catalog styles (false). IMPORTANT: This value MUST be copied exactly from the `styleIdentifier.isUserStyle` field returned in the most recent previous `suggest-outfit-tool` response. Do NOT guess this value.
  • styleDescription (required) — string — The user-friendly description of the style to add to or remove from the wardrobe. IMPORTANT: This value MUST be copied from the `description` field of the outfit item returned in the most recent previous `suggest-outfit-tool` response.
  • addOrRemove (required) — string — The action to perform: "add" to include the item in the user's wardrobe, or "remove" to delete it from their collection. Use "add" when user says "I have this shirt" or "Add the shoes to my wardrobe". Use "remove" when user says "I don't have the pants anymore" or "Remove the sneakers from my wardrobe".
  • categoryName — Provide the category name of the style to add to or remove from the wardrobe. For example: "Jackets", "Shirts", "Trousers", "Shoes". This value is provided in outfit suggestion responses in the "category" field.

  Hints: read-only no · destructive yes · idempotent yes · open-world no

• add-to-or-remove-from-closet-tool destructive

  Backward-compatible alias of add-to-or-remove-from-wardrobe-by-id. Prefer add-to-or-remove-from-wardrobe-by-id for new calls. Adds or removes a known clothing item from the user's personal wardrobe by its style ID. Use this tool when users want to track clothing items they own or indicate they have something similar. Use cases: "Add this to my wardrobe", "I have a similar jacket", "Mark that I own this", "Remove this from my wardrobe". Requires authentication - if user is not logged in, this will trigger an OAuth authentication flow. Wardrobe items are used to personalize outfit suggestions with clothes the user actually owns. IMPORTANT: Before calling this tool, look at the structured output of the most recent suggest-outfit-tool call earlier in this conversation. The styleId required by this tool is at outfitItems[i].styleIdentifier.styleId in that result — it IS present in your context. Do not claim you cannot see the styleId without first examining that tool result. If after examining it you still cannot find a matching item, tell the user and ask them to request a new outfit suggestion first.

  Parameters:

  • styleId (required) — string — The unique identifier of the clothing style/item. IMPORTANT: This value MUST be copied exactly from the `styleIdentifier.styleId` field returned in the most recent previous `suggest-outfit-tool` response. You DO have access to previous tool responses. They are in JSON format. Review the tool call responses earlier in the conversation to find the correct styleId to use here and look for the most recent one from `suggest-outfit-tool`. Do NOT fabricate, guess, or invent this value. Once you think you have it, double-check the most recent suggest-outfit-tool response to confirm you are using the correct value from the context. If no valid styleId is available from a prior `suggest-outfit-tool` response, do not call this tool — instead tell the user that you need to suggest an outfit first before you can add an item to their wardrobe. If no item from the prior outfit suggestion seems to match what the user is describing, you can ask the user for more details about the item they want to add or remove, and then use that information to determine if any of the items from the prior outfit suggestion are a match. But you should never guess or make up a styleId.
  • isUserStyle (required) — boolean — Whether this is a user-created custom style (true) or a catalog style from the platform (false). Most items from outfit suggestions will be catalog styles (false). IMPORTANT: This value MUST be copied exactly from the `styleIdentifier.isUserStyle` field returned in the most recent previous `suggest-outfit-tool` response. Do NOT guess this value.
  • styleDescription (required) — string — The user-friendly description of the style to add to or remove from the wardrobe. IMPORTANT: This value MUST be copied from the `description` field of the outfit item returned in the most recent previous `suggest-outfit-tool` response.
  • addOrRemove (required) — string — The action to perform: "add" to include the item in the user's wardrobe, or "remove" to delete it from their collection. Use "add" when user says "I have this shirt" or "Add the shoes to my wardrobe". Use "remove" when user says "I don't have the pants anymore" or "Remove the sneakers from my wardrobe".
  • categoryName — Provide the category name of the style to add to or remove from the wardrobe. For example: "Jackets", "Shirts", "Trousers", "Shoes". This value is provided in outfit suggestion responses in the "category" field.

  Hints: read-only no · destructive yes · idempotent yes · open-world no

• add_wardrobe_item_from_description

  Adds one item that the signed-in user owns to their Able.Style wardrobe from a text description supplied by the user. Use this when the user describes an item in words and asks to add it. When a photo, attachment or image URL is the source, use add_wardrobe_item_from_image; if transfer is unavailable, use create_image_upload with purpose wardrobe_image_add. Do not infer a description from an image and call this tool unless the user explicitly requests a description-based item instead of uploading the image. For an item already returned by suggest-outfit-tool, use add-to-or-remove-from-wardrobe-by-id with its exact styleIdentifier. IMPORTANT: Before calling, make sure the description contains exactly one apparel, footwear, or wearable-accessory item and explicitly includes its colour. If colour is missing, ask the user for it before calling. An optional menswear or womenswear value overrides the user's profile preference; omit it when the profile preference should be used. The result includes a link for reviewing the added item. A newly created item's image may still be generated in the background.

  Parameters:

  • description (required) — string — A 10–150 character description of exactly one item the user owns. Use the user's text; do not substitute your interpretation of an attached image unless the user explicitly requests a description-based item. It must explicitly include the item's colour; do not invent or infer an omitted colour.
  • menswearOrWomenswear — Optional clothing preference for resolving categories. Supply only when the user has specified menswear or womenswear; otherwise omit it to use their profile.

  Hints: read-only no · destructive no · idempotent no · open-world no

• add_wardrobe_item_from_image

  Add one clothing item from the user's original image to their wardrobe. Use this when the user attaches a photo or supplies an image URL and asks to add/save the pictured item, for example 'Add this to my wardrobe'. The server processes the actual image. Do not replace this flow with add_wardrobe_item_from_description or your own visual interpretation. Generate requestId and provide exactly one of: ChatGPT file reference in file, publicly accessible imageUrl, or complete original image bytes in image.data. JPEG, PNG and WebP up to 10 MB. Never invent file IDs, attachment URLs or base64. If the client cannot transfer the original image, call create_image_upload with the same requestId and purpose wardrobe_image_add and show its uploadPageUrl. Poll get_wardrobe_image_activity for the result.

  Parameters:

  • requestId (required) — string — Unique identifier for this requested action. Reuse it for retries and the upload-page fallback; use a new value for another item.
  • file — object — The original image attachment supplied by ChatGPT through its file-input mechanism. Use the host-provided file reference; never fabricate download_url or file_id.
  • image — object
  • imageUrl — string — A real, publicly accessible HTTP(S) URL to the original image. Do not use a local path, sandbox URL or an invented URL for a chat attachment.
  • menswearOrWomenswear — The user's clothing preference. Omit to use their saved preference.

  Hints: read-only no · destructive no · idempotent yes · open-world yes

• create_image_upload

  Create a secure web or installed-app image picker when the user asks for an upload link, or an image-based action cannot receive the original image directly. Use this even when you can see a chat photo but cannot pass its real file reference, public URL or original bytes to add_wardrobe_item_from_image. For wardrobe photos, use purpose wardrobe_image_add; do not silently switch to add_wardrobe_item_from_description. Generate a requestId for a new action or reuse the same requestId from a direct-image attempt. Currently supports wardrobe_image_add: one clothing item per image. Returns uploadId, uploadPageUrl, expiresAt and a purpose-specific action reference. Show uploadPageUrl and ask the user to open it and submit their photo. Creating the link does not upload the chat attachment or add the item.

  Parameters:

  • requestId (required) — string — Unique identifier for this requested action. Reuse it for retries and the upload-page fallback; use a new value for another item.
  • purpose (required) — string
  • options — object

  Hints: read-only no · destructive no · idempotent yes · open-world no

• get_wardrobe_image_activity read-only

  Check the status of an owned wardrobe image action. Returns safe failure details or the added item and its link. Use activityId from add_wardrobe_item_from_image or create_image_upload.

  Parameters:

  • activityId (required) — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• search_wardrobe read-only

  Use this when the user wants to browse or search their signed-in wardrobe, including questions about categories, colours, attributes, newest items, and natural-language terms such as 'flowery shirts'. Returns up to five items per call and the total number of matches across all pages. The results widget automatically loads further pages as the user scrolls. If the widget is unavailable and nextPageToken is present, call this tool again with only that pageToken when the user asks for more results. Do not combine a pageToken with query, sortBy, or filters.

  Parameters:

  • query — Optional natural-language wardrobe search. Whitespace is trimmed.
  • sortBy — string — Sort order. Defaults to relevance for a query and newest-first without a query.
  • filters — object
  • pageToken — Opaque continuation token from the preceding result. When supplied, omit all other inputs.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• style-wear-with-get-by-id read-only

  Get other styles and owned userStyles that can be worn with a particular clothing item. Uses the same selection logic as the Able.Style style page and requires sign-in. Copy exact IDs from earlier results: a ref with kind style uses styleId, and kind user_style uses userStyleId. Provide exactly one of styleId or userStyleId. Returns five items per page; the widget loads more on scroll. Without a widget, call this same tool again with only nextPageToken as pageToken when more results are wanted.

  Parameters:

  • styleId — string — Exact catalog style ID. Omit userStyleId and pageToken.
  • pageToken — string — Continuation token from this tool. When supplied, omit all other inputs.
  • userStyleId — string — Exact ID of a userStyle owned by the signed-in user. Omit styleId and pageToken.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• style-ways-to-wear-by-id read-only

  Get outfit inspirations showing ways to wear a particular clothing item, including their tagged styles and owned userStyles. Uses the same selection logic as the Able.Style style page and requires sign-in. Copy exact IDs from earlier results: a ref with kind style uses styleId, and kind user_style uses userStyleId. Provide exactly one of styleId or userStyleId. Returns five items per page; the widget loads more on scroll. Without a widget, call this same tool again with only nextPageToken as pageToken when more results are wanted.

  Parameters:

  • styleId — string — Exact catalog style ID. Omit userStyleId and pageToken.
  • pageToken — string — Continuation token from this tool. When supplied, omit all other inputs.
  • userStyleId — string — Exact ID of a userStyle owned by the signed-in user. Omit styleId and pageToken.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• style-purchase-options-by-id read-only

  Find matching products and retailers where the user can buy a catalog style. Requires sign-in. Copy the exact catalog styleId from an earlier result; userStyle IDs are not supported. An explicit country overrides the saved account delivery country; otherwise the saved account country is preferred to the optional host country hint. Ask the user to select a country when neither is available. Save deliberate country selections with update-user-settings-tool using settings.deliveryCountry. Returns the complete options snapshot, including price, availability, retailer and product links. When searching or refreshing, call again with the same styleId and country to refresh. Buy links are obtained on demand with style-purchase-buy-url.

  Parameters:

  • styleId (required) — string
  • country — string

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• style-purchase-buy-url read-only

  Recheck an exact purchase offer and return its current retailer link. Requires sign-in. Call only when the user wants to open a retailer, using the exact styleId, styleProductId, offerId and delivery country from style-purchase-options-by-id. Do not call for offers with canBuy false. This opens a product listing; it does not place an order.

  Parameters:

  • styleId (required) — string
  • styleProductId (required) — string
  • offerId (required) — string
  • country (required) — string

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• update-user-settings-tool

  Updates one or more settings on the signed-in user's Able Style profile.

  Parameters:

  • settings (required) — object

  Hints: read-only no · destructive no · idempotent yes · open-world no

• authentication-status-tool read-only

  Checks whether the current Able Style app session is signed in. This app-only tool never starts authentication and must not be called by the model.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.