Skip to main content
Glama

Chercher des idées de produits ou de cadeaux

chercher_produits
Read-only

Cherche dans la sélection Bazaveo (produits qui se vendent vraiment en France, avis résumés, défaut signalé, prix relevé et daté). Tous les filtres sont optionnels. Renvoie les fiches Bazaveo correspondantes. Les prix sont des relevés datés, pas des prix en direct.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chercher_produits"
  }
}

Input Schema

NameRequiredDescriptionDefault
texteNoMots à chercher dans le nom, la marque, le résumé (ex. « lego », « jeu de société »).
limiteNoNombre maximum de résultats (défaut 5, maximum 16).
publicNoPour qui : « enfants », « ados », « adultes », « famille ».
categorieNoCatégorie (ex. « jouet », « jeu de société », « lego »).
budget_maxNoBudget maximum en euros.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: results come from a curated selection, reviews are summarized, defects are flagged, and prices are dated readings rather than live prices — a data-freshness caveat the agent would otherwise get wrong.

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?

Four short sentences, front-loaded with what is searched and where, followed by optionality and the price caveat. Little waste, though the parenthetical catalog of corpus traits is slightly dense and the price caveat could have been folded in more tightly.

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?

For a read-only five-parameter search with full schema coverage and no output schema, the definition covers scope, optionality and the key return caveat (dated prices, fiches returned). What the fiche objects actually contain is left implicit, which is the main remaining gap.

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 description coverage is 100%, so all five parameters (texte, limite, public, categorie, budget_max) are already documented with examples and limits in the schema. The description only adds that every filter is optional, which is modest added meaning; baseline 3 is appropriate.

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?

States a specific verb (cherche) and a clearly scoped resource (la sélection Bazaveo), and characterizes that corpus as curated products that actually sell in France. It hints that results are fiches (renvoie les fiches Bazaveo correspondantes), which implicitly distinguishes it from the sibling fiche_produit, but never names that sibling explicitly.

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

Usage Guidelines3/5

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

Useful invocation guidance is given: all filters are optional, so the agent knows it can call with zero arguments or narrow with the five filters. However there is no explicit statement of when to use this versus fiche_produit (e.g. search first, then open a fiche for detail), so the routing is only implied.

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.

Resources