Skip to main content
Glama

MaxRechnung

GiroCode (EPC069-12) für den Rechnungsbetrag

get_invoice_girocode
Read-only

Tarif: ab Pro (darunter antwortet die API mit plan_required).

GiroCode (EPC069-12) für den Rechnungsbetrag

EPC-QR-Code (GiroCode) über den Brutto-Rechnungsbetrag auf die Absender-IBAN. Standard: JSON { object, invoice_id, payload, data_uri } — payload ist die BCD-Nutzlast, data_uri ein PNG als data:-URI. ?format=png gibt das PNG direkt zurück. 409, wenn im Absender keine IBAN hinterlegt ist oder kein positiver Betrag zu zahlen ist. Kein Betragslimit unterhalb des EPC-Maximums (999.999.999,99 €); Entwurf oder fehlende Kundendaten sind kein Hindernis. Scope invoices:read.

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

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`.
formatNo`png` liefert das QR-Bild direkt (image/png) statt JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say readOnly/no-destructive; the description goes well beyond them by disclosing the tier requirement and its error code, the default JSON response shape (`object, invoice_id, payload, data_uri`), the `format=png` direct-image mode, the 409 triggers, the EPC ceiling of 999.999.999,99 €, and the `invoices:read` scope. These are exactly the behavioral facts an agent cannot derive from structured fields.

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 plan/tier requirement is correctly front-loaded and the error and format facts follow in a dense block with no filler. Minor waste: the heading line 'GiroCode (EPC069-12) für den Rechnungsbetrag' merely repeats the title, and the parameter is referenced URL-style as `?format=png` rather than by its name `format`.

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, yet the description fully specifies the default JSON payload, the alternative PNG response, and the 409 failure cases, plus the plan and scope preconditions. Nothing an agent needs in order to call this correctly and interpret the result is missing.

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%, so both `id` and `format` are already documented, including the warning that `id` is the internal UUID rather than the document number. The description adds only the output-side distinction between default JSON and the `format=png` direct image, which the schema already states, so it earns the baseline rather than more.

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 concrete artifact: an EPC069-12 GiroCode QR code encoding the gross invoice amount against the sender's IBAN, which is clearly distinct from the PDF/XRechnung/ZUGFeRD siblings. It never explicitly contrasts itself with those siblings, but the resource is specific enough that an agent can tell what it produces.

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?

It gives useful gating context: the feature requires the Pro plan or above (otherwise `plan_required`), and it explicitly says drafts or missing customer data are not an obstacle while listing the 409 failure conditions (no IBAN on the sender, no positive amount due). It stops short of naming alternatives such as `download_invoice_pdf` when the agent actually wants a document file.

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