Skip to main content
Glama

vestiaire_search_sellers

Read-only

Find Vestiaire Collective sellers by username or first name -- a matched result's id feeds directly into vestiaire_seller.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "vestiaire_search_sellers"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSeller username or first name to search for

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / q / description
      Added value: +"Seller username or first name to search for"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world reach are covered. The description adds the id-to-vestiaire_seller handoff, which is useful chaining context, but says nothing about result limits, matching behavior, or ambiguity handling.

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?

A single sentence with zero waste; the search scope is front-loaded and the downstream chaining note follows compactly.

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?

An output schema exists, so return-value exposition is unnecessary, and annotations cover the safety profile. The description closes the loop by pointing at vestiaire_seller, though it could note result volume or when a query is too broad.

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 coverage is 100% and there is a single parameter fully documented as 'Seller username or first name to search for'. The description's 'by username or first name' merely restates the schema, adding no syntax or matching detail, so baseline 3 applies.

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) and resource (Vestiaire Collective sellers) plus the searchable fields (username or first name). It also names the downstream sibling vestiaire_seller, so an agent can distinguish this lookup tool from the seller-detail tool.

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 frames the workflow: this is the discovery step whose matched result id feeds into vestiaire_seller. That gives clear context for when to reach for it, but there is no explicit exclusion or comparison against other search-type siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.