Skip to main content
Glama
Sign In

Tracea

by io.github.Chriscorp
OverviewDiscussionsAdmin

tracea_demarche_document

Prepare le document officiel d'une demarche (CERFA ou demarche libre) et le rend signable. Appelle le generateur du backend Tracea, enregistre le dossier pour l'agent du visiteur et renvoie la reference + le chemin du PDF. A appeler APRES tracea_check_demarche (ok:true) et AVANT tracea_signature. Si des champs manquent, renvoie ok:false + champsManquants : ne fabrique jamais un document partiel.

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": {
      "id": "<id>",
      "donnees": "<donnees>",
      "agent": "<agent>"
    },
    "name": "tracea_demarche_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProcedure id (ex: 26002)
agentYesAdresse Ethereum (0x...) de l'agent du visiteur, celle de l'identite de la conversation. Ne jamais l'inventer.
donneesYesDonnees validees, memes champs que tracea_demarche_schema

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the backend generator call, that the dossier is persisted for the visitor's agent, the return payload, and the failure mode (ok:false + champsManquants) with an explicit rule against fabricating partial documents. It does not mention auth/permission requirements, which is the only notable gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: capability first, then ordering constraints, then failure behavior. Every sentence earns its place with no filler.

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 mutation tool with a nested object payload and no output schema, the description covers the side effects, sequencing, and return shape adequately. It could say more about prerequisites (e.g. required identity/auth) or what happens when the document is regenerated.

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 description coverage is 100%, so the schema already documents id, agent and donnees with their formats and warnings. The description adds only the 'same fields as tracea_demarche_schema' cross-reference, so the baseline 3 is appropriate.

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 and resource ('Prepare le document officiel d'une demarche (CERFA ou demarche libre) et le rend signable'), and names the downstream artifacts (reference + PDF path). It is clearly distinguishable from sibling tools like tracea_signature and tracea_check_demarche.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states ordering relative to siblings: 'A appeler APRES tracea_check_demarche (ok:true) et AVANT tracea_signature'. The precondition and alternative flow are spelled out, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tracea toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources