Skip to main content
Glama

Wardrobe Connect

by io.github.GoodTurnStudio
OverviewDiscussionsAdmin

Find clothes that match a description

find_clothes
Read-onlyIdempotent

Find clothes that match a short description of one item, such as "black pleated wide-leg trousers" or "cream cable-knit jumper". Takes only the item description and, if wanted, a size, a price limit, the condition and a country; it needs nothing else from the conversation. Returns eBay listings in the Clothing, Shoes and Accessories category, closest matches first and then cheapest first, plus search links for other shops and a Facebook Marketplace search phrase. Listings must match the colour, fabric and kind of garment named, 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
qYesJust 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.
sizeNoThe 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.
countryNoTwo-letter country code for the eBay site and currency. Defaults to where the request comes from.
conditionNoCondition: new, used (pre-owned) or any. Default any. pre-owned and second-hand are read as used.
max_priceNoMost to pay, in the local currency, shipping included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • 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
  2. Changed1 schema field changed
    • 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."
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), but the description adds substantial behavior beyond them: result ordering (closest match, then cheapest), match criteria (colour, fabric, garment kind, gender; kids only on request), and hard exclusions (adult/fetish/costume never shown, duplicates collapsed, suspiciously cheap listings filtered). This is exactly the extra context annotations cannot carry.

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?

Front-loaded with the purpose and an example before moving to inputs and then return/filter behavior. It is dense but every clause carries real information; the "it needs nothing else from the conversation" restatement is the only slightly redundant phrase.

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?

There is no output schema, so the description must describe returns, and it does: eBay listings in the Clothing/Shoes/Accessories category, ranking rules, plus search links for other shops and a Facebook Marketplace search phrase. Combined with the input coverage, an agent has everything needed to call and interpret this tool.

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

Parameters3/5

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

Schema description coverage is 100% and each parameter (q, size, country, condition, max_price) is already well documented with formats and defaults. The prose merely enumerates the same optional parameters ("a size, a price limit, the condition and a country") without adding syntax, units, or edge-case behavior beyond the schema.

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?

Specific verb (find) plus resource (clothes) with concrete example queries ("black pleated wide-leg trousers"), and it scopes the input to a single item's short description. That scoping implicitly separates it from the image-based sibling find_clothes_by_image.

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?

It states clearly when to use it (a short text description of one item) and explicitly says it "needs nothing else from the conversation", which is useful routing guidance for an agent holding extra context. It never names find_clothes_by_image or states the text-vs-image selection rule explicitly, so it falls short of a 5.

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

All Wardrobe Connect toolsInspect
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.

Resources