Skip to main content
Glama

xrechnung_zugferd_cross_compiler

Read-onlyIdempotent

[German XRechnung 3.0 & ZUGFeRD 2.2 / Factur-X cross-compiler & validator. Pure calculation, read-only, side-effect free]. Compiles and validates electronic invoices conforming to German national standards (KoSIT XRechnung 3.0 and hybrid PDF/A-3 ZUGFeRD 2.2), verifying Leitweg-ID routing codes and German B2B mandate compliance under the Wachstumschancengesetz. Usage: Use this tool to prepare invoices for German federal/state public sector (B2G) and German domestic B2B transactions. Returns: JSON object with { invoiceId: string, targetFormat: string, profileApplied: string, isLeitwegIdValid: boolean, isValidForGermanB2G: boolean, isGermanB2bMandateCompliant: boolean, xmlMetadataSnippet: string, taxAssessment: object }.

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": {
      "invoiceId": "<invoiceId>",
      "issueDateIso": "<issueDateIso>",
      "leitwegIdOrBuyerReference": "<leitwegIdOrBuyerReference>",
      "sellerVatOrTaxNumber": "<sellerVatOrTaxNumber>",
      "buyerName": "<buyerName>",
      "financialSummary": "<financialSummary>"
    },
    "name": "xrechnung_zugferd_cross_compiler"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerNameYesLegal name of customer or German contracting authority
invoiceIdYesInvoice number / Rechnungsnummer
currencyCodeNoCurrency (default: EUR)
issueDateIsoYesInvoice issue date (YYYY-MM-DD)
targetProfileNoZUGFeRD / Factur-X target profile
financialSummaryYesInvoice financial and tax breakdown
sellerVatOrTaxNumberYesSeller German VAT ID (USt-IdNr. DE...) or Steuernummer
isGermanPublicSectorB2GNoWhether the recipient is a German public authority requiring strict Leitweg-ID validation
leitwegIdOrBuyerReferenceYesGerman Leitweg-ID routing code (e.g. 991-12345-67) or buyer reference

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the '[Pure calculation, read-only, side-effect free]' claim largely restates them. Beyond that, the description adds real value by disclosing what is actually checked (Leitweg-ID routing codes, Wachstumschancengesetz B2B mandate) and enumerates the return object fields, compensating for the absent 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with bracketed scope and safety, followed by usage and returns in a predictable three-part layout. The bracketed preamble is slightly redundant with annotations, but overall it is dense with no filler sentences.

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

Completeness4/5

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

For a 9-parameter tool with a nested object and no output schema, the description covers what the tool verifies and enumerates the return fields, which is exactly the missing piece. It does not explain error or invalid-input behavior, which is the main residual gap.

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 every parameter including the nested financialSummary fields and the tax-category enum is already documented. The description mentions Leitweg-ID validation and profiles but adds no syntax, default, or constraint detail beyond what the schema provides; 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 (compiles and validates) and a specific resource (XRechnung 3.0 / ZUGFeRD 2.2 / Factur-X electronic invoices), plus the exact standards bodies (KoSIT) and compliance regime. Nothing else in the sibling list covers German e-invoicing, so an agent can route unambiguously.

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?

The 'Usage' line gives explicit conditions: German federal/state public sector (B2G) and German domestic B2B transactions. It does not name an alternative tool or an explicit when-not-to-use case, but the domain is narrow enough that the boundaries are effectively clear.

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