Skip to main content
Glama

Plume — French administrative forms

Ouvrir la fiche d'un formulaire, d'une lettre ou d'une démarche

ouvrir_un_document
Read-onlyIdempotent

Rend la fiche d'un résultat de chercher_un_document : pour un formulaire, à qui il s'adresse, les pièces à joindre et le lien pour le remplir en ligne avec Plume ; pour un guide, les étapes dans l'ordre avec leurs formulaires ; pour une lettre, quand l'utiliser et ce qu'il faut préparer ; pour une définition, son texte.

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

Input Schema

NameRequiredDescriptionDefault
slugYesL'identifiant rendu par la recherche.
genreYesLe genre rendu par la recherche.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the substantive behavior the annotations cannot: the tool returns a detail sheet whose content varies by genre, including the online-fill link with Plume for forms. It does not describe failure behavior for a stale slug, which keeps it short of 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?

A single sentence, front-loaded with the action and then branching by genre with parallel semicolon clauses. Dense but every clause carries a distinct payload; the only cost is that the long compound sentence requires careful reading.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does so per genre, which is exactly what an agent needs to decide between this and a sibling. The remaining gap is error/edge behavior for an unknown slug or a genre mismatch.

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% and both parameters are self-documented, so the baseline would be 3. The description adds genuine meaning by tying both `slug` and `genre` to values returned by the search tool, making the provenance and the expected pairing explicit.

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?

The description opens with a specific verb and resource ("Rend la fiche d'un résultat") and immediately anchors it to the sibling tool `chercher_un_document`, so the agent can tell it apart from searching. It then enumerates exactly what is rendered for each of the four genres (formulaire, guide, lettre, terme), which maps one-to-one onto the enum in the schema.

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?

It states clearly that the tool operates on a result produced by `chercher_un_document`, which effectively tells the agent to search first and then open. There is no explicit exclusion or statement of what to do when the item is not found, but the sequencing context is unambiguous.

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