Wardrobe Connect

Find clothes that look like a picture

find_clothes_by_image

Read-onlyIdempotent

Find clothes that look like a picture. For when the user shares or points at a picture of an outfit or item (a Pinterest pin, a saved post, a photo). Takes the image's direct https link. Returns visually similar eBay listings from the Clothing, Shoes and Accessories category only, in eBay's look-alike order. If the picture does not look like one piece of clothing (the results are scattered across unrelated kinds), matches is empty and the say line asks what the item is. A short description in q makes results match it, which removes look-alikes of the wrong kind.

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": {
      "image_url": "<image_url>"
    },
    "name": "find_clothes_by_image"
  }
}

Input Schema

Name	Required	Description
`q`	No	Which item in the picture, for example "the camel coat". Results must match it, and it is used as a fallback text search.
`size`	No	Clothing or shoe size to match, for example M, 10 or UK 8.
`country`	No	Two-letter country code for the eBay site and currency, for example US or GB.
`condition`	No	Condition: any, new or used.
`image_url`	Yes	Direct https link to a JPEG, PNG or WebP picture, 6 MB at most.
`max_price`	No	Highest price, in the local currency.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 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 for the eBay site and currency, for example US or GB."

removedInput schema / properties / country / enum

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

changedInput schema / properties / image_url / description

Previous value: -"Direct https link to one JPEG, PNG or WebP picture, 6 MB at most."New value: +"Direct https link to a JPEG, PNG or WebP picture, 6 MB at most."

removedInput schema / properties / image_url / format
```
Removed value: -"uri"
```
removedInput schema / properties / image_url / maxLength
```
Removed value: -2048
```
removedInput schema / properties / max_price / minimum
```
Removed value: -0
```

changedInput schema / properties / q / description

Previous value: -"Which item in the picture, in a few words, for example \"the camel coat\"."New value: +"Which item in the picture, for example \"the camel coat\". Results must match it, and it is used as a fallback text search."

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

Changed9 schema fields changedOct 13, 2026

changedInput schema / properties / country / description

Previous value: -"Two-letter country code for the eBay site and currency, for example US or GB."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 / image_url / description

Previous value: -"Direct https link to a JPEG, PNG or WebP picture, 6 MB at most."New value: +"Direct https link to one JPEG, PNG or WebP picture, 6 MB at most."

addedInput schema / properties / image_url / format
```
Added value: +"uri"
```
addedInput schema / properties / image_url / maxLength
```
Added value: +2048
```
addedInput schema / properties / max_price / minimum
```
Added value: +0
```

changedInput schema / properties / q / description

Previous value: -"Which item in the picture, for example \"the camel coat\". Results must match it, and it is used as a fallback text search."New value: +"Which item in the picture, in a few words, for example \"the camel coat\"."

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

Changed1 schema field changedSep 29, 2026
- changedInput schema / properties / condition / description
```
Previous value: -"any, new or used."New value: +"Condition: any, new or used."
```
First observedSep 28, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds substantial context beyond annotations: results come only from Clothing, Shoes and Accessories, are returned in eBay's look-alike order, and `matches` is empty when the picture is not a single item, with q filtering out wrong-kind look-alikes.

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?

The definition is front-loaded and mostly efficient, with each sentence adding invocation-relevant detail. It does restate the title in the opening sentence and includes several illustrative examples, but there is no serious bloat.

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

Completeness4/5

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

There is no output schema, so the description carries return-value burden. It explains key return behavior, including category restriction, look-alike order, and empty `matches` on failure, but it does not describe other possible return fields or result limits. Overall it is complete enough to invoke correctly.

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 description coverage is 100%, so the baseline is 3. The description adds meaning for q beyond the schema by explaining that a short description makes results match it and removes look-alikes of the wrong kind, which is useful operational context.

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), resource (clothes), and modality (by image/picture), and differentiates itself from the text sibling by describing look-alike image search. An agent can tell it apart from find_clothes without opening either schema.

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 triggering context: when the user shares or points at a picture of an outfit or item. It also explains fallback behavior when the image is not one piece of clothing. It does not explicitly name find_clothes as the alternative for text-only searches, so it stops short of full when/when-not/alternatives guidance.

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.