Fetch valid Vestiaire Collective condition IDs for the /vestiaire/search condition_id filter, with display names and current listing counts.
Vestiaire Collective condition values. Returns the fixed set of condition ids accepted by /vestiaire/search's condition_id filter, with each id's display name and current listing count.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries the burden. It explicitly says the tool 'returns' a fixed set, implying a read-only operation, and discloses the response contents (ids, display names, listing counts). It doesn't cover caching or rate limits, but those are minor for a zero-parameter, fixed-set lookup.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the resource and what it returns. Every word earns its place; no unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description still explains the exact return fields (id, display name, listing count) and the downstream use case. For a simple reference tool, this is complete enough for an agent to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has zero parameters, and the schema shows no required or optional properties. Since there are no parameters to describe, baseline of 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states a specific verb ('Returns') and resource ('Vestiaire Collective condition values'), and connects it to a specific consumer (/vestiaire/search's condition_id filter). It clearly distinguishes this tool from sibling reference tools like vestiaire_brands and vestiaire_categories.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description tells the agent when to use this tool: when needing condition ids for /vestiaire/search's condition_id filter. It doesn't explicitly mention alternatives or exclusions, but the context is clear and sufficient for a simple lookup.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.