Skip to main content
Glama

Modèle de lettre

get_letter
Read-onlyIdempotent

Décrit un des 64 modèles de lettres conformes de Vitef (résiliation, préavis, réclamation, mise en demeure, attestation…) : règle de droit applicable, champs à remplir, destinataires connus (Free, SFR, EDF…). La lettre se termine et s’envoie en recommandé sur la page renvoyée. Catégories : resiliation, logement, travail, argent, banque, famille, administration, auto.

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": {
      "slug": "<slug>"
    },
    "name": "get_letter"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesIdentifiant de la lettre (search_services).
providerNoDestinataire connu (slug), facultatif.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral value beyond that: it discloses the exact content returned (applicable legal rule, fields to fill, known recipients) and notes that the letter is completed and sent as registered mail on the returned page, which matters for what the agent does next. No mention of auth or rate limits, keeping it from a 5.

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 sentences, front-loaded with the core 'what it returns' claim, followed by the sending behavior and the category taxonomy. Nothing is redundant with the title. The clause 'La lettre se termine et s’envoie en recommandé' is slightly compressed and could be misread as the tool itself sending the letter.

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 two-parameter, fully documented read-only tool with no output schema, the description carries the needed burden by describing the returned record's fields and the downstream page. The only gap is procedural routing: it does not say how to obtain a valid slug or how it relates to the sibling preview/find tools.

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 100%, so the baseline is 3, but the description goes further by naming concrete known recipients (Free, SFR, EDF…) that give meaning to the optional 'provider' parameter, and by grouping the letter space into categories. It still does not explain the slug format or how to disambiguate slugs, so it does not fully exceed the 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 and resource: 'Décrit un des 64 modèles de lettres conformes de Vitef', and enumerates the letter types covered (résiliation, préavis, réclamation, mise en demeure, attestation). It also lists what the record contains (règle de droit, champs à remplir, destinataires), so the agent knows the payload shape without opening the schema. Sibling differentiation is only implicit, since preview_letter and find_reply_letter are never named.

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 implied rather than stated: the categories list tells the agent the domain of applicability, and the 's’envoie en recommandé sur la page renvoyée' clause hints this is the lookup step that precedes acting on a letter. However, there is no explicit when-to-use versus preview_letter, and no statement that the slug must first be obtained via search_services in the description itself (that hint lives only in the parameter schema).

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