Skip to main content
Glama

Fiche fournisseur

get_supplier
Read-onlyIdempotent

Détails d'un fournisseur par ID. (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": {
      "id": "<id>"
    },
    "name": "get_supplier"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant du fournisseur.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the parenthetical '(Lecture seule.)' merely restates that. It adds nothing beyond annotations: no behavior on an unknown ID, no permission or auth context, and no note on what data the record contains.

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, front-loaded sentences with the resource and lookup key first. The '(Lecture seule.)' parenthetical is redundant with the annotations and could be dropped, but there is no other waste.

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 one-parameter read tool this is nearly adequate, but with no output schema the description should say what 'détails' covers (contact info, balance, status) so an agent knows whether this call answers its question. Nothing about missing-record behavior either.

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 the single 'id' parameter is documented as an integer supplier identifier, so the schema does the work. The description's 'par ID' adds no meaning beyond it, which is the baseline 3 case.

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: fetch a supplier's details by ID. 'Par ID' implicitly separates it from the list_* siblings, but it never names or contrasts with get_customer or other single-record getters, so sibling differentiation is only partial.

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?

Usage is only implied: an agent can infer it should call this when it already holds a supplier ID. There is no explicit when-to-use, no mention of what to do without an ID, and no pointer to a search/list alternative.

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