Skip to main content
Glama

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

Convert XRechnung, ZUGFeRD, Factur-X or UBL e-invoice to JSON

einvoice_to_json
Read-only

Convert an EU e-invoice to plain JSON: 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 number, dates, seller and buyer with VAT numbers and addresses, every line with quantity, price, VAT rate and net amount, the VAT breakdown, totals and bank account. Exact values from the file, no AI. Use to book incoming e-invoices into a sheet or ERP. 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_to_json"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=false; the description is consistent with all three ('Reads or computes only and changes nothing'; 'each call is charged, so repeats are not free'), which usefully explains why idempotency is false. It also discloses pricing ($0.01/call, 25 free, failed calls free) and that values are exact with no AI, but it does not cover size limits, error behavior for unparseable files, or latency. Given annotation coverage, a 3 is fair.

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 the verb, source formats, and input modes, then return contents, then cost. It is dense but a couple of clauses (e.g. restating formats in the return sentence) could be trimmed; pricing detail is long but justified for a paid endpoint.

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?

With no output schema, the description enumerates the returned fields (invoice number, dates, parties with VAT IDs and addresses, lines with quantity/price/VAT/net, VAT breakdown, totals, bank account), plus input modes, cost model and side-effect profile. An agent has everything needed to decide and call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both url and xml are already documented, but the description adds a third input mode not represented in the schema (the file sent directly in a POST body) and frames the two parameters as interchangeable transport options. That is real meaning beyond the schema, though it stops short of explaining precedence when both are supplied.

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 ('Convert an EU e-invoice to plain JSON') and enumerates the accepted source formats (XRechnung, ZUGFeRD/Factur-X, Peppol, EN 16931 XML, embedded PDF). This clearly separates it from siblings like einvoice_create, einvoice_validate or generic xml_to_json without needing to name them.

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 a concrete use case ('book incoming e-invoices into a sheet or ERP'), which tells an agent the intended context. It does not explicitly exclude cases (e.g. validation-only or invoice creation) or name an alternative sibling, so it stops short of full routing 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.