Skip to main content
Glama

PDF herunterladen

download_document_pdf
Read-only

PDF eines Belegs herunterladen (bei E-Rechnung mit eingebettetem XML; Schweiz: QR-Zahlteil als letzte Seite, siehe payment_slip). Liefert die Datei base64-kodiert.

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

Input Schema

NameRequiredDescriptionDefault
idYesBeleg-ID
payment_slipNoSchweiz: QR-Zahlteil mitgeben (true) oder weglassen (false). Ohne Angabe gilt die Vorgabe des Belegs (hide_payment_qr)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / payment_slip
      Added value: +{
      +  "description": "Schweiz: QR-Zahlteil mitgeben (true) oder weglassen (false). Ohne Angabe gilt die Vorgabe des Belegs (hide_payment_qr)",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish read-only and closed-world behavior, yet the description still adds substantive detail: the return is base64-encoded (critical for an agent to know how to handle the payload), e-invoice PDFs carry embedded XML, and Swiss QR slips appear as the last page. File size, pagination, and error behavior remain unstated.

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?

A single dense sentence with the core action front-loaded and the two edge cases (e-invoice XML, Swiss QR) tucked into a parenthetical. Nothing is wasted, though the parenthetical stack is slightly heavy for one sentence.

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?

There is no output schema, and the description compensates by stating the return format (base64 file) and how the optional Swiss QR page affects the output. Only details like whether an unsupported document type errors out or how large files are handled are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains that the QR payment part is appended as the final page, making the real-world effect of the payment_slip flag concrete. The fallback to the document's hide_payment_qr setting is duplicated from the schema rather than extended.

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 verb and resource: downloading the PDF of a document ('Beleg'). It also distinguishes the artifact from the e-invoice XML variant by noting the PDF embeds the XML, but it never names the sibling tools (download_e_invoice_xml, download_contract_pdf, download_delivery_note_pdf) it competes with.

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 context is implied rather than stated: 'bei E-Rechnung mit eingebettetem XML' hints that this is the PDF route even for e-invoices, and the Swiss QR case is flagged. There is no explicit when-to-use / when-not and no named alternative for fetching the raw XML or contract/delivery-note PDFs.

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