InkVoice — XRechnung & E-Invoicing

Create a ZUGFeRD / Factur-X invoice

create_zugferd

Read-only

Builds a ZUGFeRD 2.x / Factur-X hybrid invoice from the same details create_xrechnung takes, and returns it as a PDF file.

A hybrid is one invoice stated twice in one file: a PDF/A-3 document a person reads, carrying the same invoice inside it as EN 16931 XML a machine books. This is the format private-sector German B2B buyers generally want, where XRechnung is what public bodies require. If the recipient is a public authority and gave you a Leitweg-ID, you want create_xrechnung instead.

The embedded XML declares plain EN 16931 — the profile ZUGFeRD calls COMFORT — not the XRechnung CIUS, because that CIUS is a statement about public-sector procurement.

Validation is identical to create_xrechnung: the same EN 16931 rules are applied before anything is built, and a rejected call names the rules and business terms that failed.

What this does NOT do:

The result is a binary PDF returned as an attachment. It is not text and there is nothing useful to read in it — do not try to quote or summarise its contents. Offer it to the user as a file.
It does not validate against veraPDF or the Mustangproject validator. The document is built to be valid PDF/A-3 with the required Factur-X metadata, but that is our reading rather than a validator's verdict.
It handles ONE tax rate and one tax category for the whole invoice, exactly as create_xrechnung does.
It does not send the invoice anywhere, and there is no Peppol.
There is no logo and no custom styling. The PDF uses the default invoice layout.

Nothing is stored: no account, no invoice record, no retained personal data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`invoice`	Yes	The invoice to turn into a ZUGFeRD / Factur-X document.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

addedInput schema / properties / invoice / properties / deliveryDate

Added value: +{
+  "default": null,
+  "format": "date",
+  "type": [
+    "string",
+    "null"
+  ]
+}

AddedSep 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only provide readOnlyHint=true and openWorldHint=false, but the description adds substantial behavioral detail: the result is a binary attachment that must be offered as a file rather than quoted or summarized, validation is performed but not via veraPDF/Mustangproject, only one tax rate/category is supported, and nothing is stored. This corroborates the readOnly annotation by explaining what 'read-only' means here, rather than repeating it.

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?

The core purpose is front-loaded in the first sentence and the structure is logical: purpose, format explanation, compliance profile, exclusions, side-effect profile. It is verbose, but nearly every section carries distinct operational value; minor redundancy exists in repeating 'exactly as create_xrechnung does' and in over-explaining the hybrid concept.

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 deeply nested schema and no output schema, the description covers return-value handling (binary PDF, offer as file), validation-failure behavior (names the rules and business terms), tax-rate limits, delivery/sending behavior, and storage side effects. An agent has everything needed to invoke it correctly and set user expectations about the output.

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% for the single invoice parameter, so the baseline is 3. The description adds the cross-reference that it takes 'the same details create_xrechnung takes' and discloses the one-tax-rate/one-tax-category constraint, but it does not add per-field meaning beyond the schema.

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?

Opens with a specific verb and resource: 'Builds a ZUGFeRD 2.x / Factur-X hybrid invoice from the same details create_xrechnung takes, and returns it as a PDF file.' It explicitly names the sibling create_xrechnung and explains the distinguishing factor (private-sector B2B vs public-sector XRechnung), so an agent can tell them apart from the description alone.

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?

States the when explicitly — 'private-sector German B2B buyers generally want' this format — and the when-not with a concrete decision rule: 'If the recipient is a public authority and gave you a Leitweg-ID, you want create_xrechnung instead.' The exclusions list (no Peppol, no sending, no veraPDF validation) further prevents accidental misuse.

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

All InkVoice — XRechnung & E-Invoicing tools Inspect

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

Need Help?