Skip to main content
Glama

Rechercher un fournisseur

search_suppliers
Read-onlyIdempotent

Recherche fournisseurs. (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_suppliers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNombre maximum de fournisseurs renvoyés (défaut 10).
queryYesNom, raison sociale, contact, code fournisseur, téléphone ou e-mail, même partiel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior1/5

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

The only behavioral claim, "(Lecture seule.)", merely repeats the already-supplied readOnlyHint=true and destructiveHint=false annotations, so it contributes nothing structured data did not already say. It says nothing about matching semantics (partial vs exact), ordering, result fields, or empty-result behavior, all of which remain undisclosed for a tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is very short and front-loaded, but it is short by under-specification rather than by efficiency. The parenthetical read-only marker is redundant with the annotations and is the only sentence that could be called wasted.

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

Completeness2/5

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

The tool is simple and the schema is fully documented, but with no output schema the description should at least say what a result contains or how matches are ranked/limited by relevance. As written, an agent knows only that it searches suppliers, which is insufficient to choose it confidently over get_supplier.

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%: the schema already explains the query accepts a name, legal name, contact, supplier code, phone or e-mail (even partial) and that limit defaults to 10. The description adds no parameter meaning 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.

Purpose2/5

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

"Recherche fournisseurs" restates the tool name (search_suppliers) and title ("Rechercher un fournisseur") almost verbatim, adding no scope, matching fields, or result description. The agent learns nothing beyond what the identifier already conveys; the sibling search_customers/search_products distinction comes from the identifiers, not the prose.

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?

There is no statement of when to use this instead of get_supplier (single-record lookup by id) or the other search_* siblings. No prerequisites, no exclusions, no note on how to follow up on results.

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