Skip to main content
Glama

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

Create XRechnung, ZUGFeRD or Factur-X e-invoice from JSON

einvoice_create
Read-only

Create an EU e-invoice from plain JSON: seller, buyer, lines with quantity, price and VAT rate, bank account. Returns XRechnung 3.0 XML (CII or UBL), a ZUGFeRD / Factur-X PDF with the XML inside, its XML alone, or EN 16931 UBL. Totals and VAT breakdown are computed and checked against the business rules first; data that breaks a rule is refused uncharged with the rule numbers. Use to issue German B2B e-invoices from a shop, ERP or workflow. 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

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": {
      "invoice": "<invoice>"
    },
    "name": "einvoice_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoxrechnung (default: XRechnung 3.0, CII syntax), xrechnung-ubl, zugferd-pdf (a readable A4 invoice as PDF/A-3 with the factur-x.xml embedded, returned as pdfBase64), zugferd (that factur-x.xml alone, EN 16931 profile) or ubl (EN 16931 UBL)
invoiceYesThe invoice as JSON: number, issueDate, dueDate, buyerReference (Leitweg-ID or order reference), seller and buyer {name, vatId, street, postCode, city, country, contactName, phone, email}, lines [{name, quantity, unit, unitPrice, vatRate}], payment {iban, bic, terms}. In a POST body send it as a JSON object. The flat fields /document/extract returns (invoice_number, seller_name, line_items…) are read too
languageNoLanguage of the labels on a zugferd-pdf page: de or en (default: de when the seller is in Germany or Austria, otherwise en)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint, destructiveHint, openWorldHint), and the description adds substantial behavior on top: totals and VAT breakdown are computed and validated first, invalid data is refused uncharged with rule numbers, and billing is $0.01/call with 25 free and failed calls free. The note that repeats are not free aligns with idempotentHint=false rather than contradicting it.

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 action and the return formats, then pricing and validation guarantees; each clause carries information. It is dense and slightly long, with mild redundancy in "Reads or computes only and changes nothing" against readOnlyHint=true.

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?

There is no output schema, and the description compensates by enumerating every return shape (XML, embedded PDF, EN 16931 UBL) and the failure mode (refusal with rule numbers). For a three-parameter generation tool that is complete enough to call correctly on the first attempt.

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 documents format, invoice and language in detail. The description primarily echoes those fields (seller, buyer, lines with quantity, price and VAT rate, bank account) and lists the output variants, adding little syntax or default logic beyond the schema. Baseline 3 is appropriate.

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 (create an EU e-invoice from plain JSON) plus the exact output formats (XRechnung 3.0 CII/UBL, ZUGFeRD/Factur-X PDF, EN 16931 UBL). This clearly separates it from einvoice_to_json and einvoice_validate, which read or check rather than generate.

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 usage context: "Use to issue German B2B e-invoices from a shop, ERP or workflow," and notes that business-rule checking happens internally before emission. It stops short of explicit when-not-to-use wording (e.g., pointing at einvoice_validate for checking an existing invoice), so it is clear context but not 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.