Skip to main content
Glama

Generate a Factur-X / ZUGFeRD PDF

generate_factur_x
Read-only

Create a Factur-X / ZUGFeRD hybrid invoice from structured invoice data: a PDF (built to PDF/A-3b rules, not certified) with the CII XML embedded as factur-x.xml and the Factur-X XMP metadata, in the EN 16931 (default), BASIC or MINIMUM profile, printed in French, German or English. The result is checked straight away with check_factur_x's checker. Returns the PDF as base64 (an embedded application/pdf resource and structuredContent.facturX.pdfBase64), the XML and the check report. MINIMUM holds only header and totals and is not a full e-invoice. Not an official tool. Uses one metered call. Requires an InvoiceVerify account (OAuth sign-in).

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": {
      "invoice": "<invoice>"
    },
    "name": "generate_factur_x"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the printed invoice. Default: French for a seller in France, German for Germany/Austria, else English.
invoiceYesInvoice data: {number, issueDate (YYYY-MM-DD), dueDate?, deliveryDate?, currency?, buyerReference?, orderReference?, note?, paymentTerms?, seller: Party, buyer: Party, payment?: {meansCode, iban?, bic?, paymentReference?}, lines: [{name, quantity, unitPrice, unitCode?, vatCategory? (S,Z,E,AE,K,G,O), vatRate?}]}. Party: {name, vatId?, companyId?, street?, city?, postalCode?, country (ISO 2), endpointId? with endpointScheme? (e.g. 0225 for a SIREN), contactEmail?}. Unlike generate_invoice, the electronic address is optional. Full schema: InvoiceData in /openapi.json.
profileNoFactur-X profile: 'EN 16931' (default; the profile France's reform names), 'BASIC' or 'MINIMUM'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: one metered call, an OAuth-gated InvoiceVerify account, automatic self-checking via check_factur_x, and an explicit 'not certified' PDF/A-3b caveat. It also discloses the exact return payload (base64 PDF, XML, check report) with both the resource and structuredContent.facturX.pdfBase64 locations.

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 artifact and profile/format options before the operational caveats, and no sentence is filler. It is dense and runs long, packing caveats about profiles, billing, and auth into a single paragraph, which makes it slightly harder to scan than it could be.

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?

For a tool with a nested invoice payload, no output schema, and metered billing, the description covers output shape, cost, auth, and output limitations (unnamed/uncertified PDF/A, MINIMUM not a full e-invoice). Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond it by explaining what MINIMUM actually contains (header and totals only) and how the profile affects the output. The invoice object's structure is left to the schema, which is appropriate given the coverage.

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?

Names a specific verb and artifact: create a Factur-X/ZUGFeRD hybrid invoice PDF with embedded CII XML and XMP metadata. It distinguishes itself from generate_invoice (electronic address optional) and from check_factur_x (which it invokes automatically), so an agent can pick it without opening the 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?

Gives clear context for use: profile choice with EN 16931 as the default and the caveat that MINIMUM is not a full e-invoice, plus the French/German/English printing options. It does not explicitly state when an agent should prefer a sibling such as generate_invoice or check_factur_x over this tool, so it stops short of full routing guidance.

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