Skip to main content
Glama

eRechio – E-Rechnungen prüfen

E-Rechnung prüfen (XRechnung, ZUGFeRD-XML)

rechnung_pruefen
Read-only

Prüft eine E-Rechnung (XRechnung UBL/CII oder ZUGFeRD-/Factur-X-XML) gegen XML-Schema, EN 16931 und die KoSIT-Regeln XRechnung 3.0.2 und erklärt jede Meldung auf Deutsch (was bedeutet der Regelcode, wie beheben). Braucht einen eRechio-API-Schlüssel (Header Authorization: Bearer pk_…); jede erfolgreiche Prüfung zählt ein Dokument im Monatskontingent. Prüft nicht die inhaltliche oder steuerliche Richtigkeit. Keine PDF-Annahme: bei ZUGFeRD die eingebettete XML-Datei senden.

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": {
      "xml": "<xml>"
    },
    "name": "rechnung_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlYesDie Rechnung als XML-Text (UTF-8), höchstens 2 MB.
idempotency_keyNoOptional, 1–255 sichtbare ASCII-Zeichen. Gleicher Schlüssel und gleiche Rechnung innerhalb von 24 Stunden liefern das gespeicherte Ergebnis und zählen nicht erneut.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations: discloses the required API key header format (Bearer pk_…), that each successful check consumes one document from the monthly quota, and the exact scope boundary of the validation. The idempotency_key behavior is also explained. It does not describe response shape or error behavior for failed validations, which keeps it from a 5.

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?

Four sentences, each doing distinct work: purpose and standards, return behavior (explains every message in German), auth/quota cost, and scope/format caveats. Front-loaded with the purpose, with no filler or repetition.

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?

No output schema exists, yet the description covers the return value (per-message German explanations of rule codes and fixes), the authentication prerequisite, the billing/quota consequence, and the input format caveat. Nothing an agent needs to invoke this correctly is missing.

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 coverage is 100%, so both parameters are already documented. The description does add real meaning for the xml parameter by clarifying that ZUGFeRD/Factur-X must be sent as the embedded XML rather than the PDF, which prevents a common wrong invocation, but it adds nothing beyond the schema for idempotency_key.

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 (prüft) and resource (E-Rechnung) and enumerates the supported formats (XRechnung UBL/CII, ZUGFeRD-/Factur-X-XML) plus the validation targets (XML-Schema, EN 16931, KoSIT XRechnung 3.0.2). An agent can tell immediately that this is a standards-conformance validator, not a general invoice reader.

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 negative scoping: it does not check inhaltliche oder steuerliche Richtigkeit, and it warns not to send a PDF but the embedded XML for ZUGFeRD. It stops short of naming the sibling 'status' tool or stating when to prefer it (e.g. checking quota before validating), so alternative-routing guidance is implicit 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