Skip to main content
Glama

MaxRechnung

Beleg abrufen

get_invoice
Read-only

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

Beleg abrufen

Liefert den Beleg zu {id} — Rechnung, Korrektur (KR-) oder Storno (ST-). type im Body unterscheidet sie; eigene Abruf-Endpunkte für Korrektur/Storno gibt es nicht.

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

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds plan availability across all tiers and — importantly, since there is no output schema — that the returned body carries a `type` field distinguishing invoice vs correction vs cancellation. It says nothing about error behavior for missing ids or whether documents are returned as metadata only.

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?

Compact and front-loaded: plan availability, then the core operation, then the document-type caveat. The 'Beleg abrufen' line merely repeats the title and earns no place, but the rest is tight for the information conveyed.

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?

For a one-parameter read tool with full schema coverage and read-only annotations, this covers what an agent needs: how to obtain the id, what kinds of documents come back, and that no separate endpoint exists for corrections/cancellations. Only the absence of any error/empty-result expectation keeps it from a 5.

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% and the single `id` parameter is documented in detail (internal UUID, not the document number, with `list_invoices` given as the way to resolve a number). The description only restates `{id}`, so the schema is doing the substantive work; 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?

States a specific verb and resource ('Liefert den Beleg zu `{id}`') and immediately enumerates the three document kinds it can return (Rechnung, Korrektur `KR-`, Storno `ST-`). That scoping makes it distinguishable from narrower siblings like get_invoice_summary or get_invoice_audit, though it does not explicitly contrast with get_sales_document or get_payment.

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?

Adds a genuine routing rule: corrections and cancellations are fetched through this same tool, since 'eigene Abruf-Endpunkte für Korrektur/Storno gibt es nicht' — that prevents an agent from hunting for a separate endpoint. The tier line ('in jedem Tarif') sets availability context. It stops short of an explicit when-not statement, so it lands below a 5.

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