Skip to main content
Glama

E-Invoice Reader - XRechnung, ZUGFeRD, Factur-X, UBL to JSON

e_invoice_reader
Read-onlyIdempotent

Read an EU e-invoice (XRechnung UBL or CII, ZUGFeRD / Factur-X PDF with embedded XML, Peppol UBL) and get clean JSON: seller, buyer, VAT IDs, invoice number, dates, line items, net/VAT/gross totals, IBAN, payment terms, plus checks (totals add up, IBAN valid, mandatory fields present) and CSV of the lines. Germany requires receiving e-invoices since 2025. Runs on our server, nothing stored. Free: 25 calls/day per IP. Paid: $0.01 per call via x402 at https://radarbg.com/x402/e-invoice-reader.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "e_invoice_reader"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlNoThe e-invoice XML as text
fileNameNoOptional file name, e.g. invoice.pdf
fileContentNoOr base64 of the XML or the ZUGFeRD/Factur-X PDF

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld/idempotent annotations by disclosing that processing runs on the vendor's server with nothing stored, that the free tier is capped at 25 calls/day per IP, and that paid calls cost $0.01 via x402 with a URL. It also previews the validation checks performed, which is exactly the operational context an agent needs.

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-loads the purpose and accepted formats, then output, then operational notes and pricing, with no filler sentences. The middle stretch is a dense run-on that mixes return contents with validation checks, but every clause carries information.

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?

With no output schema, the description properly compensates by listing the returned fields, the checks, and the CSV of lines. The one real gap is that zero parameters are marked required, and the description never states that at least one of xml/fileContent must be supplied or how conflicts are resolved.

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 the three parameters are already documented in the schema, and this sets the baseline at 3. The description only indirectly hints at parameter choice by mentioning PDF-with-embedded-XML handling, without clarifying precedence between xml, fileName, and fileContent.

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 and resource ('Read an EU e-invoice') and enumerates the concrete formats handled (XRechnung UBL/CII, ZUGFeRD/Factur-X PDF, Peppol UBL). It also names the output shape (JSON with seller, buyer, VAT IDs, totals, checks, CSV lines), which clearly separates it from write-side siblings like invoice_generator or sepa_xml.

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 when this applies (receiving EU e-invoices, German 2025 mandate) and what inputs are acceptable. It does not explicitly route to or away from any sibling tool, and no exclusions are stated, so it stops short of full when/when-not 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