Skip to main content
Glama

Check a Factur-X / ZUGFeRD invoice (free)

check_factur_x
Read-onlyIdempotent

Free, no sign-in needed: check a Factur-X or ZUGFeRD hybrid invoice for France's e-invoicing reform (and Germany). Send the PDF as base64 (pdf_base64), or only its CII XML (xml). Finds the embedded factur-x.xml / zugferd-invoice.xml, identifies the profile (MINIMUM, BASIC WL, BASIC, EN 16931, EXTENDED) and whether France's reform accepts it, checks the PDF/A-3 attachment and XMP metadata at a basic level, and runs 316 rules on the XML (the EN 16931 business rules plus InvoiceVerify's own checks). Returns pass/warn/fail per check with plain-language fixes. Not an official validator (no full PDF/A-3 conformance, XSD or EXTENDED-CTC-FR rules). The document is not stored. PDFs up to 3 MB. Shares the 20 free calls per hour per connection with check_peppol_receivability and search_peppol_directory.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_factur_x"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlNoOnly the embedded CII XML (factur-x.xml), when there is no PDF. Container checks are then skipped.
filenameNoOriginal file name, shown in the report.
pdf_base64NoThe Factur-X / ZUGFeRD PDF, base64-encoded (a data: URL prefix is accepted). Send this or xml.
include_xmlNoAlso return the embedded XML read from the PDF (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/closed-world, and the description adds substantial behavior beyond them: the document is not stored, PDFs capped at 3 MB, and a 20 calls/hour limit shared with check_peppol_receivability and search_peppol_directory. It also discloses scope limits (316 rules, basic XMP/PDF-A-3 checks) that shape how the agent should interpret results.

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 purpose and access terms, then inputs, then scope limits and rate limits; nearly every sentence carries information. The middle clause about profile enumeration and reform acceptance is dense but earns its place.

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?

With no output schema, the description explains the return shape (pass/warn/fail per check with plain-language fixes) and the limits of that output. Combined with the input and rate-limit notes, an agent has everything needed to call it and interpret results 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 description coverage is 100%, so the schema already documents pdf_base64, xml, filename and include_xml. The description restates the either/or input choice and notes the xml-only path skips container checks, but adds little meaning beyond what the schema already conveys.

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 ('check a Factur-X or ZUGFeRD hybrid invoice'), then names the sub-tasks: profile detection, reform acceptance, PDF/A-3 attachment check, 316 XML rules, and pass/warn/fail output. This distinguishes it from format-specific siblings like check_si_ubl and from generate_factur_x.

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?

Gives clear when-to-use context (free, no sign-in, France's reform and Germany) and exclusions ('not an official validator, no full PDF/A-3 conformance, XSD or EXTENDED-CTC-FR rules'). It does not explicitly name the sibling to redirect to for a full validation, so the routing to alternatives is implied rather than explicit.

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