Skip to main content
Glama

Plume — French administrative forms

Transmettre les réponses de la personne et obtenir le lien pour remplir

transmettre_les_reponses

Quand la personne vous a donné ses réponses pour un formulaire de la bibliothèque (trouvé avec chercher_un_document), transmettez-les ici : Plume rend un lien court à lui donner. En l'ouvrant, elle retrouve le formulaire dans l'éditeur de Plume, ses réponses prêtes : un clic les met dans le message à Pluma, l'assistante de Plume, qui remplit les cases et ne demande que ce qui manque. Les règles habituelles du site s'appliquent (essai gratuit, pages, paiement). Écrivez une information par ligne, « libellé : valeur » (« Nom de naissance : Martin »), 3500 caractères au plus. Le lien vaut une seule fois et 24 heures au plus ; les réponses sont gardées chiffrées, puis effacées dès qu'elles sont affichées ou à l'échéance. Ne donnez le lien qu'à la personne.

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>",
      "reponses": "<reponses>"
    },
    "name": "transmettre_les_reponses"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesL'identifiant (`slug`) d'un formulaire rendu par `chercher_un_document`.
reponsesYesLes réponses de la personne, une information par ligne : « Nom de naissance : Martin ».

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly=false, destructive=false, idempotent=false), while the description adds substantial unseen behavior: the link is single-use and valid at most 24 hours, answers are stored encrypted and deleted after display or at expiry, and the site's usual rules (free trial, pages, payment) apply. This is exactly the extra context annotations cannot convey and it is consistent with idempotentHint=false.

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?

Front-loaded with the trigger condition, then the effect, then constraints (format, size, link lifetime, privacy). Dense and mostly earning its place, though the Plume/Pluma editor narrative is longer than strictly needed for tool selection.

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?

There is no output schema, and the description explains the return value precisely: a short link to hand to the person, plus what happens when it is opened. Combined with the parameter and privacy details, an agent has everything needed to invoke and relay the result correctly.

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?

Schema coverage is 100%, including maxLength 3500 and the `slug` provenance from `chercher_un_document`, so the schema already documents both parameters. The description restates the "libellé : valeur" line format and the 3500-character cap, adding little beyond structured data; baseline 3 applies.

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 states a specific verb and resource — transmettez les réponses and Plume rend un lien court — and anchors the request to a form found with `chercher_un_document`. An agent can distinguish it from `chercher_un_document`/`ouvrir_un_document` without opening either 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?

The trigger condition is explicit: use it when the person has given their answers for a library form found with `chercher_un_document`. It also constrains link sharing ("Ne donnez le lien qu'à la personne"), but does not state an explicit when-not or name an alternative flow for obtaining the form itself.

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