Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vestiaire_suggest

Fetch Vestiaire Collective search-box autocomplete suggestions for partial queries, returning matching brands and completed search phrases.

Instructions

Vestiaire Collective search-box autocomplete. Returns Vestiaire Collective's own search-box autocomplete suggestions for a partial query: matching brands plus completed search phrases. Public data, sourced from Vestiaire Collective's own search-suggestions service.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesPartial search query to autocomplete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the data is public and sourced from Vestiaire's own service, but doesn't disclose any limitations, error behavior, response format, or whether it requires authentication. Minimal behavioral detail beyond the basic function.

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 two sentences, front-loaded with the purpose. It is efficient with no extraneous fluff, though there is slight redundancy in repeating 'search-box autocomplete' and 'search-suggestions service'. Still, it's appropriately sized for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple autocomplete tool with one parameter and no output schema, the description gives enough to understand the core function and what it returns (brands plus phrases). However, it doesn't specify the response structure or edge cases (e.g., empty query, pagination), and it doesn't explicitly differentiate from other Vestiaire tools, leaving some ambiguity for an agent choosing among siblings.

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?

The input schema has 100% coverage with a clear description for the single parameter 'q' ('Partial search query to autocomplete'). The description adds little beyond this, only mentioning 'partial query' again. Baseline 3 applies since the schema already documents the parameter well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool provides search-box autocomplete suggestions for a partial query, naming the resource (Vestiaire Collective) and the action (returns suggestions). It distinguishes itself from other Vestiaire tools like vestiaire_search by focusing on autocomplete, but doesn't explicitly name the sibling, so it's slightly less clear for differentiation.

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

Usage Guidelines2/5

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

The description mentions 'for a partial query' which implies when to use it, but there is no explicit guidance about when to use this tool versus alternatives like vestiaire_search or vestiaire_brands. No exclusions or alternative tool names are given, leaving the agent to infer the use case.

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

Deploy Server

Other Tools