Skip to main content
Glama

Livraisons

list_deliveries
Read-onlyIdempotent

Liste les livraisons en cours/terminées. (Lecture seule.)

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": "list_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoPériode : les N derniers jours, aujourd'hui compris (défaut 30).
limitNoNombre maximum de livraisons renvoyées (défaut 20).
statusNopending = en attente, assigned = confiée à un livreur, in_transit = en route, delivered = livrée, failed = échouée, cancelled = annulée. Vide = toutes.

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=true, idempotentHint=true and destructiveHint=false, so '(Lecture seule.)' merely repeats structured data and adds no credit. The description discloses nothing about ordering, pagination behavior, or how 'days' interacts with 'status', and its framing of 'en cours/terminées' undersells the pending/failed/cancelled states the schema supports.

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?

Two short fragments with zero padding, but the brevity comes at the cost of under-specification rather than disciplined editing. It is front-loaded but says almost nothing.

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 filtered-list tool with annotated safety and fully described parameters, nothing critical is missing, but the description omits result ordering and does not clarify the apparent tension between its 'in progress/completed' scope and the six-value status enum.

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 'status' parameter even enumerates each value in French, so the schema carries the full burden. The description 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 ('Liste les livraisons') with a scope qualifier ('en cours/terminées'). It does not differentiate itself from the sibling get_delivery, which fetches a single delivery, so it falls 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?

There is no when-to-use guidance, no exclusion against get_delivery, and no statement about prerequisites. The agent must infer from the name alone that this is the bulk-list counterpart to the single-record fetch.

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