Skip to main content
Glama

MaxRechnung

PDF des Belegs

download_sales_document_pdf
Read-only

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

PDF des Belegs

Serverseitig gerendertes PDF (DIN 5008) — Lieferscheine ohne Preise, mit Unterschriftszeile. Kein 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_sales_document_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesInterne `id` des Belegs (UUID), nicht die Belegnummer. Zu einer Nummer (z. B. `AN-2026-0004`) liefert `GET /sales-documents?number=…` (MCP: `list_sales_documents` mit `number`) die `id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false), so the description's job is to add context, and it does: rendering is server-side, layout follows DIN 5008, delivery-note variants omit prices and include a signature line, and no DRAFT watermark is applied. The remaining gap is delivery mechanics — whether the result is raw bytes, base64, or a link — which is left unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the line "PDF des Belegs" merely duplicates the title field and the leading plan-availability fragment is front-loaded as a sentence without a verb. The genuinely informative DIN 5008 / watermark details are buried at the end rather than leading.

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?

With one required parameter, full schema coverage, annotations, and no output schema, the definition covers what the tool produces content-wise. It is still incomplete for a download tool because it never says how the PDF is returned to the caller, which is the one thing an agent needs to handle 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 `id` property description already explains that it is the internal UUID rather than the Belegnummer and how to obtain it via `list_sales_documents`. The prose 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 states the resource and the concrete artifact produced: a server-rendered PDF of the Beleg following DIN 5008, with delivery notes carrying no prices and a signature line, and no DRAFT watermark. That is more specific than a restatement of the title, though it never names the sibling `download_invoice_pdf` or otherwise distinguishes invoice PDFs from sales-document PDFs.

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 usage-adjacent statement is plan availability ("in jedem Tarif (Free, Pro, Business)"), which is a licensing constraint rather than a when-to-use rule. Nothing says when to call this instead of `get_sales_document` or `download_invoice_pdf`, nor whether draft documents are acceptable, so an agent must infer the trigger condition.

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