Skip to main content
Glama

Plume — French administrative forms

Chercher un formulaire, une lettre ou une démarche

chercher_un_document
Read-onlyIdempotent

Cherche dans la bibliothèque de Plume : formulaires administratifs français (cerfa, CAF, MDPH, impôts…), modèles de lettres (attestation d'hébergement, résiliation…), guides de démarche (vendre sa voiture, demander le RSA…) et définitions. Accepte un numéro de cerfa ou des mots de tous les jours. Rend le titre, un résumé, le genre et l'identifiant (genre, slug) de chaque résultat, avec l'adresse de sa page sur plumeai.fr.

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": {
      "requete": "<requete>"
    },
    "name": "chercher_un_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
genresNoLes collections à interroger (toutes par défaut).
maximumNoNombre de résultats (12 au plus).
requeteYesCe que la personne cherche : « carte grise », « 15776 »…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: it discloses the fields returned per result (title, summary, genre, slug) and the page URL, which matters because there is no output schema. It does not discuss ranking or what happens on zero matches, keeping it below 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 search scope and followed by input flexibility and return shape. The parenthetical enumerations are long but each item illustrates a distinct collection, so little is wasted; a slightly tighter phrasing would earn a 5.

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?

For a three-parameter read-only search with no output schema, the description covers scope, accepted input forms, default behavior, and the exact fields returned. An agent has everything needed to call it and interpret results without opening the schema.

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 adds real meaning: it clarifies that 'requete' accepts either a cerfa number or plain-language terms, and that all collections are searched by default. That goes beyond the schema's own examples and default note.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Cherche') and a specific resource (the Plume library), then enumerates the four content collections it covers. The return-shape sentence ('Rend le titre, un résumé, le genre et l'identifiant') makes clear this is a discovery tool, which naturally separates it from ouvrir_un_document and transmettre_les_reponses.

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?

Gives clear context for when to reach for it: administrative forms, letter templates, procedure guides, definitions, and it explicitly says a cerfa number or everyday words are both acceptable queries. It does not state exclusions or name a sibling as the alternative for opening/acting on a result, so it stops short of full routing guidance.

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