Skip to main content
Glama

FacturLint - Factur-X 1.09.2 & BR-FR-CTC E-Invoicing

repair_facturx_envelope

Action payante / authentifiée : répare automatiquement l'enveloppe technique PDF/A-3b, le flux XMP Factur-X et l'ICC sRGB sans jamais modifier les montants comptables.

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": {
      "pdf_base64": "<pdf_base64>"
    },
    "name": "repair_facturx_envelope"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdf_base64YesFichier PDF Factur-X défectueux encodé en Base64.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 substantial work: it declares a paid, authenticated mutation, defines the repair scope as purely technical, and explicitly guarantees accounting amounts are never modified — a critical safety boundary. Remaining gaps are that it does not say whether the original file is overwritten or a repaired copy is returned, and what happens when repair is impossible.

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?

A single front-loaded sentence that leads with the cost/auth caveat and the action, then narrows scope, then states the safety guarantee. No filler.

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

Completeness2/5

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

There is no output schema, so the description must explain what comes back after repair — a repaired file, a status, a set of fixed components? It says nothing about the return value or failure behavior. For a billing-relevant repair operation, that is a meaningful omission.

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?

Only one parameter, and its schema description already states it fully ('Fichier PDF Factur-X défectueux encodé en Base64'). The description adds nothing about format, size limits, or whether an output path is expected. With 100% schema coverage, the baseline 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?

Names a specific verb (répare automatiquement) and enumerates the exact components touched: PDF/A-3b envelope, XMP Factur-X flow, sRGB ICC. That is far more precise than a generic 'repair PDF', and it implicitly distinguishes the action from the read-only siblings (validate_facturx, explain_facturx_rule). It stops short of a 5 only because it never contrasts itself with those siblings by name.

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?

The phrase 'Action payante / authentifiée' signals prerequisites (cost, credentials) that select when this tool can be used at all, which is genuinely useful context. However, it never states the triggering condition — e.g. use after validate_facturx reports an envelope defect — nor any exclusion. Usage is implied rather than stated.

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.