Skip to main content
Glama

validate_facturx

Valide de manière 100 % déterministe (sans stockage) une facture Factur-X 1.09.2 (PDF/A-3b ou XML CII) contre les schémas XSD officiels, le Schematron EN 16931 et les règles françaises BR-FR-CTC.

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": {
      "content_base64": "<content_base64>"
    },
    "name": "validate_facturx"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameNoNom optionnel du fichier (ex: facture.pdf ou factur-x.xml).
content_base64YesContenu binaire du fichier PDF Factur-X ou XML CII encodé en Base64.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 disclose meaningful traits: fully deterministic, stateless (sans stockage), and the precise rule sets applied. It stops short of saying what a failed validation returns (error list, severity, rule identifiers), which matters for a validator with no output schema.

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 dense sentence with the key qualifiers (deterministic, stateless, version, formats, rule sets) front-loaded and no filler. Every clause earns its place.

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

Completeness3/5

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

The input side is well covered, but with no output schema the description should explain the shape of the validation result (valid/invalid plus rule violations). That return-value gap leaves the definition incomplete for a validator whose whole value is its report.

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 both parameters (filename, content_base64) are already documented in the schema. The description adds no extra meaning about encoding, size limits, or how filename affects format detection, so the 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 names a specific verb (valide), a specific resource (facture Factur-X 1.09.2), the accepted input formats (PDF/A-3b or XML CII), and the exact validation layers (XSD, Schematron EN 16931, BR-FR-CTC). The verb alone separates it cleanly from the siblings explain_facturx_rule and repair_facturx_envelope.

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?

Usage is only implied: an agent can infer this is the check step before repair or explanation, but the description never states when to call it versus repair_facturx_envelope or explain_facturx_rule, nor any preconditions. No exclusions or alternatives are given.

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