Skip to main content
Glama

Aides à la rénovation énergétique (France)

Lire un dossier public

lire_fiche
Read-onlyIdempotent

Rend le texte complet d’un dossier, d’un guide ou d’une fiche publics, par son identifiant.

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

Input Schema

NameRequiredDescriptionDefault
slugYesIdentifiant de la fiche, tel que rendu par la recherche ou la liste.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the meaningful point that the full text of the document is returned (not just metadata), which is useful beyond the annotations, but it says nothing about truncation, size limits, or what happens when the slug does not exist.

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?

A single front-loaded sentence that states the return value, the resource types and the key, with no filler. It is not padded, though the phrase 'dossier, d'un guide ou d'une fiche' could arguably be compressed to one word.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple read-only single-parameter tool with full annotation coverage, a documented parameter and no output schema, and the description covers both the resource and the expected output (full text). Nothing essential an agent needs in order to call it correctly is missing.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains the slug and where it comes from. The description only restates that the identifier refers to the fiche/dossier/guide, adding no format or validity guidance beyond the schema, so the baseline of 3 applies.

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?

The description gives a specific verb and result ('Rend le texte complet') plus the resource ('dossier, guide ou fiche publics') and the lookup key ('par son identifiant'), so an agent knows exactly what comes back and what input is needed. It does not name a sibling such as lister_fiches or rechercher_connaissances to explain why this tool rather than those, so it stops short of 5.

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: 'par son identifiant' suggests an identifier must be obtained first, and the schema note points at search or list as its source, but the description itself never states when to use this versus lister_fiches or rechercher_connaissances. There are no exclusions or prerequisites spelled out.

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