Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

E-invoice validation: XRechnung, ZUGFeRD, Factur-X or UBL e-invoice

einvoice_validate
Read-only

Validate an EU e-invoice: send XRechnung, ZUGFeRD / Factur-X (XML or the PDF that embeds it), Peppol or other EN 16931 XML as text, as a file in a POST body or by URL. Returns valid or not and every broken business rule with its number (BR-CO-15, BR-DE-15…), the field, a plain message and the fix. Checks a subset of the EN 16931 and XRechnung 3.0 rules: sums, VAT, mandatory fields. Use before sending an e-invoice or when one is rejected. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
urlNoAbsolute public http(s) URL of the e-invoice: an XML file or a ZUGFeRD / Factur-X PDF (or send `xml`, or the file in a POST body)
xmlNoThe e-invoice XML as text (CII or UBL), up to 5 MB in a POST body
profileNoauto (default: the German XRechnung rules run when the file names XRechnung), xrechnung or en16931

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 annotations by disclosing real limits (only a subset of EN 16931 and XRechnung 3.0 rules: sums, VAT, mandatory fields), the shape of the result (broken rule numbers like BR-CO-15, field, message, fix), and an explicit cost model ($0.01/call, first 25 free, failed calls free, repeats not free). Consistent with readOnlyHint=true and destructiveHint=false; the 'each call is charged' note is coherent with idempotentHint=false.

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 purpose and accepted formats, then coverage limits, then usage timing, then pricing. Dense but nearly every clause carries information; the final sentence bundles read-only, billing and non-free-repeat facts into one long run-on, which slightly hurts scannability.

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 three optional params, no output schema and rich annotations, the description covers inputs, output content, rule-coverage caveats and cost, which is enough to call it correctly. Minor gaps: no precedence rule when multiple input modes are combined (that detail lives only in the schema) and no mention of the 5 MB limit in prose.

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 schema already explains url, xml and profile. The description's 'as text, as a file in a POST body or by URL' restates the three input modes but adds no new syntax or precedence rules (e.g. what happens if both url and xml are supplied), so it lands at the baseline.

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?

Names a specific verb (validate) and resource (EU e-invoice) plus the exact formats accepted (XRechnung, ZUGFeRD/Factur-X XML or PDF, Peppol, EN 16931 XML). It is clearly distinguishable from the sibling creation/conversion tools such as einvoice_create and einvoice_to_json.

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 concrete timing cues: 'Use before sending an e-invoice or when one is rejected.' That is clear context, but no explicit alternative sibling (e.g. invoice_check or vat_validate) is named or ruled out, so it stops short of full when/when-not routing.

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.