Besot: Musician Fashion Resale

search_pieces

Read-onlyIdempotent

Find where to buy a specific piece of clothing or footwear connected to the people we obsess over, and get every live resale listing for it in one call.

Use this when someone asks questions like: where can I buy the Gucci HA HA HA blazer; is the Ivy Park Drip 2 hoodie listed in a medium; what is the Pleasing crewneck going for right now; which platforms have the Oasis adidas Original Forever trainers in a UK 9; what Beatles Comme des Garcons pieces are on the resale market today.

Most of these garments are sold out at retail and exist only on resale, scattered across marketplaces under inconsistent seller titles. besot gives each garment one canonical name and pulls the live listings for that exact piece from eBay, StockX, GOAT, The RealReal, Vestiaire, Grailed, Poshmark, Mercari and Depop.

Covers clothing and footwear that the people we obsess over designed, founded, were the inspiration for, or wore. Takes plain language in q (for example "Ivy Park Drip 2 hoodie" or "Harry Styles Gucci blazer"), with optional filters for artist, brand, collection, garment type, size, condition, source platform, and price range.

Every listing returned carries the platform, size, condition, price (approximate USD, null when the seller did not state one), and a direct buy link.

Input Schema

Name	Required	Description
`q`	No	Free text over piece name, collection, artist, brand, and garment vocabulary. Product names are canonical (Gazelle, Firebird Track Top), so plain garment words work too, in British or American English: trainers or sneakers, jumper or sweater, trousers or pants, trackie or tracksuit.
`size`	No	Match a listing size; call get_facets for valid values
`sort`	No
`type`	No	COLLECTION type: Collab, Capsule, or Own brand. For the garment, use category.
`brand`	No	Designer/brand name
`limit`	No	1-50, default 20
`artist`	No
`source`	No	Resale platform, e.g. ebay, grailed, therealreal
`category`	No	GARMENT category, one of: footwear, outerwear, tops, knitwear, hoodies, bottoms, one-pieces, suits, sets, accessories, eyewear, swim-active
`maxPrice`	No
`minPrice`	No
`condition`	No
`collection`	No	Collection id (exact)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedJul 13, 2026

addedInput schema / properties / category

Added value: +{
+  "description": "GARMENT category, one of: footwear, outerwear, tops, knitwear, hoodies, bottoms, one-pieces, suits, sets, accessories, eyewear, swim-active",
+  "maxLength": 100,
+  "type": "string"
+}

changedInput schema / properties / q / description

Previous value: -"Free text over piece name, collection, artist, brand"New value: +"Free text over piece name, collection, artist, brand, and garment vocabulary. Product names are canonical (Gazelle, Firebird Track Top), so plain garment words work too, in British or American English: trainers or sneakers, jumper or sweater, trousers or pants, trackie or tracksuit."

changedInput schema / properties / type / description

Previous value: -"Collab, Capsule, or Own brand"New value: +"COLLECTION type: Collab, Capsule, or Own brand. For the garment, use category."

Changed9 schema fields changedJul 6, 2026
- addedInput schema / properties / artist / maxLength
```
Added value: +200
```
- addedInput schema / properties / brand / maxLength
```
Added value: +200
```
- addedInput schema / properties / collection / maxLength
```
Added value: +200
```
- addedInput schema / properties / condition / maxLength
```
Added value: +100
```
- addedInput schema / properties / q / maxLength
```
Added value: +500
```
- addedInput schema / properties / size / maxLength
```
Added value: +100
```
- addedInput schema / properties / sort / maxLength
```
Added value: +100
```
- addedInput schema / properties / source / maxLength
```
Added value: +200
```
- addedInput schema / properties / type / maxLength
```
Added value: +100
```
First observedJun 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered; the description adds genuinely new behavior — that listings are aggregated live from nine named platforms, that besot normalizes inconsistent seller titles to one canonical garment name, and that prices are approximate USD and null when unstated. The main omission is pagination/total-count behavior for a tool capped at 50 results.

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

Conciseness3/5

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

The purpose is front-loaded in the first sentence, but the body runs five paragraphs with repetition — the 'people we obsess over' framing and the retail-sold-out rationale are each restated, and the nine-platform list duplicates what the source parameter already enumerates. The example queries earn their space; the surrounding prose could be cut by a third without losing information.

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?

For a 13-parameter search tool with no output schema, the description does the important work of describing the return shape (platform, size, condition, approximate USD price, direct buy link). It stops short of covering result ordering, total result counts, or what an empty result means for a sold-out piece, which matters given the 'sold out at retail' premise.

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?

At 62% schema coverage the description compensates by enumerating the filter axes (artist, brand, collection, garment type, size, condition, source platform, price range) and by giving plain-language q examples plus the British/American vocabulary hint. It does not resolve the type-vs-category ambiguity that the schema flags, and it calls the garment filter 'garment type' while the actual parameter is 'category' — a small but real mismatch.

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 where to buy') applied to a specific resource ('a specific piece of clothing or footwear connected to the people we obsess over') and adds the outcome ('every live resale listing for it in one call'). The scope sentence about garments sold out at retail and scattered across marketplaces makes it clearly distinguishable from get_piece (detail lookup) and get_facets (value enumeration).

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?

Provides five concrete example questions that map directly onto use cases ('is the Ivy Park Drip 2 hoodie listed in a medium', 'what is the Pleasing crewneck going for right now'), which is stronger than generic when-to-use prose. However, it never names a sibling or states when NOT to use it — e.g. that get_piece should be used once a piece is already identified, or get_facets for valid size values.

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

All Besot: Musician Fashion Resale 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.

Resources

Need Help?