Skip to main content
Glama

process_german_einvoice

Generate PDF/A-3 invoices, embed ZUGFeRD/Factur-X XML, or validate and extract XRechnung 3.0 and EN 16931 e-invoices for German B2B compliance.

Instructions

Generate PDF/A-3 invoices, embed ZUGFeRD/Factur-X XML, or validate/extract XRechnung 3.0 & EN 16931 e-invoices.

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": "process_german_einvoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoTarget EN 16931 / ZUGFeRD / Factur-X / XRechnung profile.EN16931
xml_urlNoOptional HTTP/HTTPS URL of existing ZUGFeRD/XRechnung XML for 'embed' mode.
file_urlNoPublic HTTP/HTTPS URL of PDF or XML input for 'embed' or 'extract' mode.
operationNoOperation mode: 'generate' (PDF/A-3 + XML), 'embed' (XML into PDF), or 'extract' (validate & parse).generate
xml_base64NoOptional Base64-encoded XML string for 'embed' mode.
file_base64NoBase64-encoded PDF or XML input alternative to 'file_url'.
invoice_dataNoStructured invoice JSON payload for 'generate' or 'embed' mode.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does not state side effects, whether outputs are returned inline or stored, file-size or network-fetch limits for the URL inputs, or failure behavior for invalid XML. The one behavioral hint is the word 'validate' in the extract mode, which suggests a read/check operation, but nothing distinguishes the mutating generate/embed modes from the read-only extract mode.

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 front-loaded sentence with three parallel clauses that mirror the three operations, and no filler. Every clause earns its place by naming a distinct mode and its output standard.

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?

With seven optional parameters, no annotations, and no required fields, the agent most needs guidance on which input combination each mode requires and what happens when inputs conflict; the description does not provide it, though the output schema does relieve it of explaining return values. Adequate but with clear gaps for a multi-mode tool.

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 operation and profile enums is already documented with per-mode guidance in the schema. The description adds no syntax, format, or mutual-exclusivity information (e.g. xml_url vs xml_base64) beyond what the schema provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names specific verbs tied to concrete resources: generate PDF/A-3 invoices, embed ZUGFeRD/Factur-X XML, validate/extract XRechnung 3.0 and EN 16931 invoices. This maps cleanly onto the three operation enum values, so an agent can tell what the tool does. It stops short of naming the sibling tools it is distinct from, though the German e-invoicing domain is self-evidently different from the KYB/lead/tender siblings.

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?

The three modes are stated, which implies when each is used, but the description never says how to choose between generate, embed, and extract, nor what prerequisites each mode imposes (e.g. that extract needs file_url or file_base64, embed needs a source PDF plus XML). Usage is inferable only by cross-reading the operation enum in the schema.

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