Skip to main content
Glama

MaxRechnung

PDF der Rechnung

download_invoice_pdf
Read-only

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

PDF der Rechnung

Serverseitig gerendertes PDF (DIN 5008). Entwürfe tragen das ENTWURF-Wasserzeichen.

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

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

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds genuinely new behavioral context: the document is server-side rendered to DIN 5008 and drafts carry an ENTWURF watermark, which tells the agent what it will actually receive. It still does not say how the PDF is returned (binary stream, base64, or link).

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?

Short and front-loaded: plan availability, then what the artifact is, then the rendering and watermark details. The repeated heading line 'PDF der Rechnung' duplicates the title, but nothing else is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter PDF download with no output schema, the description covers the artifact's nature and a visible caveat (draft watermark). The missing piece is the return mechanism — whether the caller gets binary data, a URL, or a base64 payload — which matters because there is no output schema to answer it.

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 id property description already explains that it is the internal UUID rather than the document number, including how to look it up via list_invoices. The description adds nothing further 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 the resource and output form precisely: 'PDF der Rechnung' plus 'Serverseitig gerendertes PDF (DIN 5008)'. It does not distinguish itself from close siblings such as download_invoice_xrechnung or download_invoice_zugferd, which also deliver invoice documents, so an agent must infer the difference.

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

Usage Guidelines2/5

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

The only guidance is plan availability ('in jedem Tarif') and the draft-watermark note. There is no statement of when to choose this plain PDF over the XRechnung or ZUGFeRD variants, and no prerequisites or side effects are described, so an agent gets little help in tool selection.

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