Skip to main content
Glama

Outil.io

Get letter tracking

get_letter_tracking
Read-only

Suivi d’un courrier Merci Facteur (id = envoiId renvoyé par send_letter) : impression, remise à La Poste, distribution.

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_letter_tracking"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the informational payoff by enumerating the tracked stages (printing, handover to La Poste, distribution), but does not describe the returned payload, polling behaviour, or how long tracking data remains available.

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

Conciseness5/5

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

One front-loaded sentence with no filler: the resource, the id provenance, and the stage list all appear in the first pass. Nothing is redundant with the title or annotations.

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 one-parameter read-only lookup with no output schema, the description supplies the needed context: what is tracked, which stages exist, and where the id comes from. It could go slightly further on the shape of the response, but nothing essential to invoking it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single 'id' property is undocumented in the schema, so the description carries the burden — and it does, defining id precisely as the envoiId returned by send_letter. That is meaningful provenance an agent could not infer from the bare string schema.

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 ('Suivi d'un courrier Merci Facteur') and distinguishes itself from send_letter by tying the input to that tool's output. It stops short of naming an alternative tracking source, but the scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical '(id = envoiId renvoyé par send_letter)' establishes the precondition and sequencing: call send_letter first, then use its returned envoiId here. No explicit when-not-to-use guidance is given, which prevents a 5.

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.