Skip to main content
Glama

Rechercher un produit

search_products
Read-onlyIdempotent

Recherche produits par nom/référence/code-barres. (Lecture seule.)

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNombre maximum de produits renvoyés (défaut 10).
queryYesNom, référence ou code-barres du produit, même partiel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so '(Lecture seule.)' merely restates structured data and earns no credit. The description adds nothing beyond annotations — no statement about partial-match behavior, empty-result handling, result ordering, or that limit caps the returned set.

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?

Two short sentences, front-loaded with the purpose, with no filler text. The parenthetical '(Lecture seule.)' is redundant rather than harmful, costing only a small amount of efficiency.

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 two-parameter read tool with full schema coverage and no output schema, the definition is minimally viable. It still leaves matching semantics (substring vs. fuzzy), ordering, and result-shape expectations unspecified, which an agent would need in order to interpret a returned list correctly.

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 both 'query' (name, reference, or barcode, even partial) and 'limit' (default 10) are already fully documented in the schema. The description adds no syntax, format, or matching-rule detail beyond that, so the baseline 3 applies.

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 and resource ('Recherche produits') and enumerates the matchable fields (nom/référence/code-barres), which is more than the name alone conveys. It does not differentiate from siblings such as get_product or the low-stock/top-product listings, so an agent must infer that this is the free-text lookup variant.

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?

No explicit when-to-use or when-not-to-use statement; the only signal is that it is a search, which implicitly contrasts with get_product by identifier. Nothing tells the agent whether to prefer this over get_product when it already holds a reference, or how results are ranked.

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