Skip to main content
Glama

Détail d'une livraison

get_delivery
Read-onlyIdempotent

Détails d'une livraison (avec livreur, adresse, dernière position GPS). (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_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant de la livraison.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/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 repeats structured data and earns no credit. The genuinely additive part is the disclosure of what the payload contains (livreur, adresse, dernière position GPS), which matters because no output schema exists, though nothing is said about behavior on a missing or invalid id.

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 compact parenthetical clauses, front-loaded with the resource and payload contents. Slightly wasteful because the '(Lecture seule.)' clause duplicates the readOnlyHint annotation instead of adding new information.

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 single-parameter read-only getter with full schema coverage and annotations covering the safety profile, the description supplies the one thing structured fields lack: the shape of the returned detail. Only the error/empty-result behavior is unaddressed, which is minor here.

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% and the single 'id' parameter is already documented as the delivery identifier, so the schema does the heavy lifting. The description adds no format, range, or sourcing guidance for that id, which is the baseline-3 case for a one-parameter tool.

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+resource ('Détails d'une livraison') and enumerates what the retrieved detail contains (livreur, adresse, dernière position GPS), which clearly separates it from a bulk lister like list_deliveries. It does not name a sibling explicitly, so it stops short of a 5.

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 never says when to call this instead of list_deliveries or any other lookup, and gives no prerequisites or conditions. Usage is only inferable from the singular 'd'une livraison' and the required id.

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