Skip to main content
Glama

MaxRechnung

E-Rechnung (XRechnung 3.0.2 / CII-XML)

download_invoice_xrechnung
Read-only

Tarif: in jedem Tarif (Free, Pro, Business).

E-Rechnung (XRechnung 3.0.2 / CII-XML)

XRechnung 3.0.2 (CII-XML nach EN 16931, XRechnung-CIUS 3.0.2 der KoSIT; gegen den KoSIT-Validator geprüft). Ohne Accept-Header: das XML als Datei-Download. Mit Accept: application/json: { filename, warnings, xml } — warnings listet offene Punkte (z. B. fehlende Leitweg-ID/BT-49). Das XML wird beim Festschreiben eingefroren und danach unverändert ausgeliefert.

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": {
      "id": "<id>"
    },
    "name": "download_invoice_xrechnung"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesInterne `id` der Rechnung (UUID), nicht die Belegnummer. Zu einer Nummer (z. B. `RE-2026-0004`) liefert `GET /invoices?number=…` (MCP: `list_invoices` mit `number`) die `id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already mark this read-only and non-destructive, but the description adds genuinely new behavior: content negotiation via the Accept header, the exact JSON envelope { filename, warnings, xml }, the meaning of warnings (e.g. missing Leitweg-ID/BT-49), and the fact that the XML is frozen at finalization and returned unchanged thereafter. That immutability detail is exactly the kind of context annotations cannot carry.

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?

The download mechanics and return shapes are front-loaded and compact. There is mild waste: the title line is repeated verbatim inside the description and the plan-availability sentence (Free, Pro, Business) is billing boilerplate that does not help an agent invoke the tool.

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 compensates fully by describing both response modalities and the fields of the JSON variant. For a one-parameter read tool, an agent has everything needed to call it correctly and interpret the result.

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% and the single parameter is already documented in-schema, including the id-vs-Belegnummer distinction and a pointer to list_invoices with number. The description adds nothing about the parameter, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and standard: XRechnung 3.0.2 (CII-XML per EN 16931, KoSIT CIUS 3.0.2) delivered as a file download, which is unmistakably distinct from a PDF or ZUGFeRD sibling in substance. It does not explicitly name those siblings as alternatives, so an agent must infer the routing rather than read it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage guidance is limited to invocation shape: no Accept header yields a file download, Accept: application/json yields JSON. There is no statement of when to choose XRechnung over download_invoice_pdf or download_invoice_zugferd, nor prerequisites such as whether the invoice must already be finalized — that stays implicit in the closing sentence.

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