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 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

TableJSON 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)

TDQS

A4.5/5.0

Behavior5/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint false. The description adds value by detailing the scope (fandom style), multi-platform aggregation, and output specifics (platform, size, condition, price with reliability note, buy link). No contradictions.

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 description is informative but slightly verbose. It starts with the core purpose, provides examples, and explains scope and output. Every sentence adds value, but it could be tightened without losing clarity.

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?

Given the tool has 13 parameters and no output schema, the description covers purpose, scope, and output fields. It explains what data is returned but could better describe search matching logic and edge cases like no results.

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 62%. The description explains the 'q' parameter's plain-language usage and references get_facets for valid size values. Other parameters are covered by schema descriptions; the description adds context but could be more detailed for some optional filters.

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?

The description clearly states the tool finds where to buy specific pieces of clothing/footwear and returns live resale listings. It directly distinguishes itself from siblings like get_facets and list_collections by focusing on search across pieces.

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?

The description provides explicit usage examples and contexts (e.g., 'Use this when someone asks questions like: ...'). It implies the tool is for resale items but does not explicitly state when not to use it or compare to alternatives.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: listing collections, getting filter facets, searching for pieces, and retrieving listings for a specific piece. The descriptions explicitly guide when to use each, leaving no ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case: get_facets, get_piece, list_collections, search_pieces. No mixing of styles or conventions.

Tool Count5/5

Four tools is well-scoped for the domain of browsing and searching musician fashion resale. Each tool earns its place, covering the key operations without being under- or over-provisioned.

Completeness5/5

The tool surface covers the complete workflow: listing collections, searching pieces with facets, getting full listings for a specific piece. No obvious gaps for the intended read-only search/browse use case.

Resources

Need Help?