Besot: Musician Fashion Resale

Server Details

Cross-source price compare for clothing musicians designed, wore, or founded. Real listings.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Last Tested: 2026-09-07 11:09
Transport: Streamable HTTP
URL

Available Tools

4 tools

get_facetsA

Read-onlyIdempotent

Inspect

Return the values that actually exist in the catalogue for filtering a search: sizes, conditions, source platforms, artists, designers, and the price range.

Use this before search_pieces when you want to build a precise query from real values rather than guesses. For example, to check which sizes of a garment are genuinely listed right now, or which platforms currently carry a given collection.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4.8/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds that it returns 'values that actually exist in the catalogue', reinforcing real-time snapshots. No contradiction; slightly adds context beyond annotations.

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

Conciseness5/5

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

Two short paragraphs: first states what it returns, second gives usage guidance. Every sentence is purposeful, with no redundancy. Front-loaded with core function.

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?

Given no parameters and no output schema, the description adequately covers what facets are returned and when to use. With annotations providing safety and idempotency context, it's fully informative for agent decision-making.

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

Parameters5/5

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

No parameters exist, so baseline is 4. The description adds value by listing the types of facets returned (sizes, conditions, etc.), which the schema cannot convey. This fully compensates for missing parameter details.

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 it returns facet values for filtering, specifying categories like sizes, conditions, artists. It distinguishes from sibling tools like search_pieces (used for actual searching) and get_piece/list_collections, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises using this tool before search_pieces to build precise queries from real values, with examples like checking sizes or platforms. This provides clear guidance on when to use versus alternatives.

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

get_pieceA

Read-onlyIdempotent

Inspect

Get the complete set of live resale listings for one specific garment, with a direct buy link for each.

Call search_pieces first: it returns the collectionId and pieceId this tool needs.

Use this once someone has settled on a specific piece and wants every option available: all platforms, all sizes, all conditions, with prices wherever a live feed provides one. For example, after a search surfaces the Ivy Park Drip 2 Oversized Hoodie, use this to show every listing of it currently for sale and where to buy each one.

ParametersJSON Schema

Name	Required	Description	Default
`pieceId`	Yes
`collectionId`	Yes

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds context: returns 'live resale listings', 'direct buy link', 'all platforms, all sizes, all conditions, with prices wherever a live feed provides one.' 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.

Conciseness5/5

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

The description is concise, with three paragraphs each providing essential information. No fluff or redundant statements.

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?

No output schema exists, but the description explains the output: 'live resale listings with direct buy link', 'all platforms, all sizes, all conditions, with prices.' It mentions that pieces have a collectionId and pieceId and that this tool is used after search_pieces. Complete for a detailed lookup tool.

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 0%, but the description explains that pieceId and collectionId come from search_pieces and are needed for identifying the garment. It does not describe each parameter individually, but the added context about where to get the IDs compensates.

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 verb 'Get' and the resource 'the complete set of live resale listings for one specific garment, with a direct buy link for each.' It distinguishes from siblings by mentioning that search_pieces is called first and that this tool provides all listings for a specific piece.

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 explicitly says when to use: 'Use this once someone has settled on a specific piece and wants every option available.' It also provides a prerequisite: 'Call search_pieces first: it returns the collectionId and pieceId this tool needs.' Does not explicitly state when not to use, but the context is clear.

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

list_collectionsA

Read-onlyIdempotent

Inspect

List the collections Besot indexes: collaborations between the people we obsess over and design houses, capsule drops, and brands they founded and own.

Use this when someone asks what a given artist has made, which artists have worked with a given brand, or what is covered before running a search. For example: what fashion has Harry Styles designed; which artists have collaborated with adidas; what Beatles clothing collections exist.

Coverage includes Harry Styles (Gucci HA HA HA, Pleasing), Beyonce (Ivy Park with adidas), Oasis, Liam Gallagher and Noel Gallagher (adidas), and The Beatles (Comme des Garcons, Stella McCartney, Alice + Olivia), and grows as new fandoms are added.

Filter by artist, or by type: collaboration, capsule, or artist-founded brand.

ParametersJSON Schema

Name	Required	Description	Default
`type`	No	Collab, Capsule, or Own brand
`artist`	No

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already convey readOnly, openWorld, idempotent, non-destructive. Description adds that coverage 'grows as new fandoms are added,' which is useful context for the open world hint. 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?

Well-structured with three paragraphs, front-loaded with main purpose. Could be slightly more concise but every sentence adds value.

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?

Despite no output schema, the description provides sufficient context for a read-only listing tool: what it covers, examples, and filter options.

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 has 50% description coverage (only type described). Description clarifies type values ('collaboration, capsule, or artist-founded brand') and explains filtering usage, compensating for missing schema info.

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 'List the collections Besot indexes' with specific examples of collaborations, capsules, and brands. It distinguishes itself from sibling tools like search_pieces by focusing on collections.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use this tool: 'when someone asks what a given artist has made, which artists have worked with a given brand, or what is covered before running a search.' Provides concrete examples.

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

search_piecesA

Read-onlyIdempotent

Inspect

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.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

1 tool updateJul 13, 2026

Changedsearch_pieces3 fields changed

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

3 tool updatesJul 6, 2026
- Changedget_piece2 fields changed
  - addedInput schema / properties / collectionId / maxLength
```
Added value: +200
```
  - addedInput schema / properties / pieceId / maxLength
```
Added value: +200
```
- Changedlist_collections2 fields changed
  - addedInput schema / properties / artist / maxLength
```
Added value: +200
```
  - addedInput schema / properties / type / maxLength
```
Added value: +100
```
- Changedsearch_pieces9 fields changed
  - 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
```
4 tool updatesJun 30, 2026
- First observedget_facets
- First observedget_piece
- First observedlist_collections
- First observedsearch_pieces

Frequently Asked Questions

Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.

Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
- GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
- HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
- DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.

The HTTP ownership file has this structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "claim": "glama_claim_..."
}

Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.

If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.

For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

LowlandData Resale & SecondhandOAuth
io.github.AdrienHq
GDPR-clean secondhand listings and sold comps for resale pricing research. No seller personal data.
E-commerce & Retail Research & Data
1
lemmebuyit-mcpOAuth
com.lemmebuyit
Search 86 US retailers — 260M+ products with real-time pricing, stock, and price history.
E-commerce & Retail Search
2
Remode - Visual Fashion Shopping
io.github.deviljin17
Visual fashion search across retailers and resale, with localized prices and app handoffs.
E-commerce & Retail Image & Video Processing
2
SoundCreation Catalog A
ro.soundcreation
Search 52,000 musical instruments and audio products: live prices, deals, bundles, open-box units.
E-commerce & Retail Search
61

Related MCP Servers

ShopSignal
E-commerce & Retail Search
codesk90
F
license
Not graded
quality
D
maintenance
DTC competitor intelligence: catalog snapshots, price history, cross-brand product comparison, and drop/restock detection for 84 Shopify-powered brands. Pay-per-call via Apify.
Updated 4 months ago (2026-05-22 22:28 UTC)
-
Secondhand MCP
E-commerce & Retail Browser Automation Search
jlsookiki
A
license
A
quality
A
maintenance
Enables AI assistants to search secondhand marketplaces (Facebook Marketplace, eBay, Depop, Poshmark) for used items with filters like price, condition, size, and color.
Updated 6 days ago (2026-09-01 06:13 UTC)
3
208
64
MIT
japan-market-mcp
E-commerce & Retail Web Scraping Search
atushi1841
F
license
Not graded
quality
B
maintenance
Enables AI agents to search and compare prices across Japanese used camera, watch, luxury brand, and instrument marketplaces from multiple stores, returning price, brand, condition, and source store information.
Updated 21 days ago (2026-08-17 11:06 UTC)
-
troedlerofficial
E-commerce & Retail Web Scraping Search
JumpLink
A
license
Not graded
quality
B
maintenance
Enables searching multiple second-hand marketplaces simultaneously from a local command line or AI assistant, providing unified results with pricing insights while respecting each source's terms and robots.txt.
Updated 2 days ago (2026-09-05 11:53 UTC)
MIT

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?

Server Details

Available Tools

Tool Schema Changelog

Frequently Asked Questions

Discussions

Related MCP Connectors

Related MCP Servers

troedlerofficial

Glama MCP Gateway

Resources