Skip to main content
Glama

Wardrobe Connect

Find clothes that match a description

find_clothes
Read-onlyIdempotent

Find clothes that match a description. Use when the user describes a piece of clothing they want ("black pleated wide-leg trousers", "cream cable-knit jumper like the one I saved"). Natural requests are fine ("a navy midi wrap dress for a summer wedding under £60 in a size 12"): the occasion is kept out of the search and returned in occasion, and a price or size in the words is used when max_price or size is not passed. Returns eBay listings in the Clothing, Shoes and Accessories category, closest matches first and then cheapest first (from a best-match and a price-sorted search), plus search links for other shops and a Facebook Marketplace search phrase. Listings must match the colour and fabric named, the same kind of garment (by title and by eBay category, so socks never answer a search for trainers), and men's or women's if given; kids' items only when asked for. Adult, fetish and costume listings are never shown, repeat listings of the same item count once, and listings far below the typical price for the search (usually bait or junk) are left out

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesA clear description of the item: colour, type, fabric or style, brand if known.
sizeNoThe user's size, for example M, XL, 12, UK 9, US 8.5, EU 39 or W32. Numbers without UK, US or EU are read in the country's usual sizes. Dress and shoe sizes are converted between UK, US and EU, and dress sizes to S, M and L. Listings that state a different size are left out; listings that state the size come first (size_listed true), then ones that don't say.
countryNoTwo-letter country code. Defaults to where the request comes from. Supported: US, GB, IE, CA, AU, DE, FR, IT, ES.
conditionNonew, used (pre-owned) or any. Default any. pre-owned and second-hand are read as used.
max_priceNoMost the user wants to pay, in their local currency, shipping included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial operational context: source (eBay Clothing/Shoes/Accessories), ranking order (best-match then price), dedup of repeat listings, exclusion of adult/fetish/costume and price-outlier 'bait' listings, and the extra search links returned. This is far beyond what the annotations disclose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and usage are front-loaded, but the trailing block is a long, comma-heavy enumeration of filtering and ranking rules. Every clause carries information, yet it could be broken into shorter sentences for easier scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does: listings, ordering, and the auxiliary shop/Facebook search links, plus the filtering rules. An agent has everything needed to call it and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the structured baseline already documents all five parameters; the description nonetheless adds real semantics, notably that a price or size mentioned in the query words is honoured when max_price or size is omitted, which is cross-parameter behaviour the schema does not express.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Find') and resource ('clothes') scoped to a natural-language description rather than an image, which implicitly separates it from the only sibling, find_clothes_by_image. The detail about matching colour, fabric and garment kind makes the scope of the search unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use when the user describes a piece of clothing they want' and gives worked examples of natural requests, plus how occasion, price and size words in the query are handled. It never names the sibling tool as the alternative for image input, so the when-not is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.