Skip to main content
Glama

Eigene Brief-PDF hochladen

letter_upload_pdf

Lädt einen fertigen Brief als PDF hoch, der genau so verschickt wird, wie er ist. Die Prüfung schaut, ob die Empfängeradresse im Adressfeld der Versandart steht. Beim Standardbrief liegt es 60 bis 85,5 mm von oben, beim Einschreiben 68 bis 85,5 mm, jeweils 22 bis 107,5 mm von links. Der übrige Fensterbereich bleibt leer, an jeder Kante bleiben 5 mm frei, und jede Seite ist A4 hochkant. Zurück kommen pdfStorageKey, die Funde mit den Millimetern zum Verschieben und Seite 1 mit eingezeichneten Zonen. sendable sagt, ob order_send diesen pdfStorageKey annimmt. Weichen nur PLZ oder Ort ab, lassen sich entweder die Empfängerfelder oder die PDF korrigieren; jeder andere Fund braucht eine korrigierte PDF und einen neuen Upload. Kostenlos. EN: Uploads a finished letter PDF that is sent exactly as it is. The check looks at whether the recipient address sits in the address zone of the delivery method. For a standard letter that is 60 to 85.5 mm from the top, for Einschreiben 68 to 85.5 mm, both 22 to 107.5 mm from the left. The rest of the window area stays empty, every edge keeps 5 mm clear, and every page is A4 portrait. The result holds pdfStorageKey, the findings with the millimetres to move, and page 1 with the zones drawn in. sendable says whether order_send accepts this pdfStorageKey. When only the postcode or city differs, either the recipient fields or the PDF can be corrected; every other finding needs a corrected PDF and a new upload. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "letter_upload_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdfUrlNoÖffentliche URL der Brief-PDF (Alternative zu pdfBase64). EN: Public URL of the letter PDF (alternative to pdfBase64).
pdfBase64NoDie Brief-PDF als Base64 (Alternative zu pdfUrl). EN: The letter PDF as Base64 (alternative to pdfUrl).
reasoningNo
deliveryTypeNoVersandart, für die das Adressfeld geprüft wird; dieselbe wie später bei order_send. Standard standard. EN: Delivery method the address zone is checked for; the same one order_send gets later. Defaults to standard.
recipientZipNoOptional: PLZ des Empfängers, wird mit der gedruckten Adresse verglichen. EN: Optional: recipient postcode, compared with the printed address.
recipientCityNoOptional: Ort des Empfängers, wird mit der gedruckten Adresse verglichen. EN: Optional: recipient city, compared with the printed address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / deliveryType / description
      Previous value: -"Versandart, für die das Adressfeld geprüft wird; dieselbe wie später bei order_send. Standard standard. EN: Delivery method the address zone is checked for; the same one you will pass to order_send. Defaults to standard."New value: +"Versandart, für die das Adressfeld geprüft wird; dieselbe wie später bei order_send. Standard standard. EN: Delivery method the address zone is checked for; the same one order_send gets later. Defaults to standard."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the exact millimetre tolerances per delivery method, the 5 mm edge margin, A4 portrait requirement, that the operation is free, and precisely what the response contains (pdfStorageKey, findings with millimetres, annotated page 1, sendable). It also explains the correction paths, which is exactly the behavioral context an agent needs.

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?

Front-loaded and information-dense, but the full German text is duplicated verbatim in English, roughly doubling length. Every sentence is useful, yet the bilingual mirroring is redundant for a single reader.

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?

With no output schema, the description carries the return-value burden and does so fully: it names every returned field and its meaning, plus the sendable gate for order_send. Nothing an agent needs to call or interpret the result is 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 already 83%, so the baseline is 3; the description adds real value by tying deliveryType to the same value order_send will receive and explaining that recipientZip/recipientCity are compared against the printed address. The pdfUrl/pdfBase64 alternation is left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Lädt einen fertigen Brief als PDF hoch') and immediately scopes it as a finished PDF sent exactly as-is, which distinguishes it from letter_create_draft and attachment_upload_pdf. The validation purpose (address zone check) is spelled out concretely.

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?

Explains the context of use (finished PDF, checked against the delivery method, later consumed by order_send) and gives remediation guidance for findings. It does not explicitly name the alternative tool for generating a letter instead of uploading one, so it stops short of full when-not guidance.

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.