Wardrobe Connect

Find clothes that match a description

find_clothes

Read-onlyIdempotent

Find clothes that match a description. For 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "find_clothes"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	A clear description of the item: colour, type, fabric or style, brand if known.
`size`	No	The 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.
`country`	No	Two-letter country code. Defaults to where the request comes from. Supported: US, GB, IE, CA, AU, DE, FR, IT, ES.
`condition`	No	Condition: new, used (pre-owned) or any. Default any. pre-owned and second-hand are read as used.
`max_price`	No	Most the user wants to pay, in their local currency, shipping included.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedNov 9, 2026

changedInput schema / properties / country / description

Previous value: -"Two-letter country code for the eBay site and currency. Defaults to where the request comes from."New value: +"Two-letter country code. Defaults to where the request comes from. Supported: US, GB, IE, CA, AU, DE, FR, IT, ES."

removedInput schema / properties / country / enum

Removed value: -[
-  "US",
-  "GB",
-  "IE",
-  "CA",
-  "AU",
-  "DE",
-  "FR",
-  "IT",
-  "ES"
-]

changedInput schema / properties / max_price / description

Previous value: -"Most to pay, in the local currency, shipping included."New value: +"Most the user wants to pay, in their local currency, shipping included."

removedInput schema / properties / max_price / minimum
```
Removed value: -0
```

changedInput schema / properties / q / description

Previous value: -"Just the item, in a few words: colour, type, fabric or style, and brand if known, for example \"navy midi wrap dress\". Up to 100 characters, with no other conversation text or personal details."New value: +"A clear description of the item: colour, type, fabric or style, brand if known."

removedInput schema / properties / q / maxLength
```
Removed value: -100
```

changedInput schema / properties / size / description

Previous value: -"The size to match, for example M, XL, 12, UK 9, US 8.5, EU 39 or W32. Dress and shoe sizes are converted between UK, US and EU."New value: +"The 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."

removedInput schema / properties / size / maxLength
```
Removed value: -20
```

Changed8 schema fields changedOct 13, 2026

changedInput schema / properties / country / description

Previous value: -"Two-letter country code. Defaults to where the request comes from. Supported: US, GB, IE, CA, AU, DE, FR, IT, ES."New value: +"Two-letter country code for the eBay site and currency. Defaults to where the request comes from."

addedInput schema / properties / country / enum

Added value: +[
+  "US",
+  "GB",
+  "IE",
+  "CA",
+  "AU",
+  "DE",
+  "FR",
+  "IT",
+  "ES"
+]

changedInput schema / properties / max_price / description

Previous value: -"Most the user wants to pay, in their local currency, shipping included."New value: +"Most to pay, in the local currency, shipping included."

addedInput schema / properties / max_price / minimum
```
Added value: +0
```

changedInput schema / properties / q / description

Previous value: -"A clear description of the item: colour, type, fabric or style, brand if known."New value: +"Just the item, in a few words: colour, type, fabric or style, and brand if known, for example \"navy midi wrap dress\". Up to 100 characters, with no other conversation text or personal details."

addedInput schema / properties / q / maxLength
```
Added value: +100
```

changedInput schema / properties / size / description

Previous value: -"The 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."New value: +"The size to match, for example M, XL, 12, UK 9, US 8.5, EU 39 or W32. Dress and shoe sizes are converted between UK, US and EU."

addedInput schema / properties / size / maxLength
```
Added value: +20
```

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / condition / description

Previous value: -"new, used (pre-owned) or any. Default any. pre-owned and second-hand are read as used."New value: +"Condition: new, used (pre-owned) or any. Default any. pre-owned and second-hand are read as used."

First observedSep 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, openWorld, idempotent, non-destructive), yet the description adds substantial behavioral detail beyond them: sort order (closest then cheapest), result composition (eBay listings plus links for other shops and a Facebook Marketplace phrase), and hard filters (colour/fabric/category matching, no adult/fetish/costume, dedup, exclusion of bait-priced outliers). This is unusually rich disclosure.

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?

It is long, but front-loaded with purpose and every clause carries a distinct rule (filtering, sorting, dedup, price-outlier removal). Dense rather than padded; a mild deduction for packing many rules into one block.

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 takes on the burden of describing return values and does so: listings with closest-then-cheapest ordering, search links for other shops, a Facebook Marketplace phrase, and the `occasion` field. An agent knows what calling this yields.

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 baseline is 3, but the description adds real meaning on top: the occasion in the query is stripped from the search and surfaced in an `occasion` field, and price/size mentioned in the words are honored only when max_price/size are absent. That precedence rule is not derivable from the schema alone.

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 matching a described item), and the sibling find_clothes_by_image is implicitly distinguished because this tool takes a text description rather than an image. An agent can tell the two apart immediately.

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?

Gives clear context on when to use it: natural-language requests are fine, and it explains how conversational price/size/occasion phrases are handled. It never explicitly names find_clothes_by_image as the alternative for image input, which is the one missing routing hint.

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

All Wardrobe Connect tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.