Skip to main content
Glama

PDF-Anhang hochladen

attachment_upload_pdf

Lädt ein PDF als Anhang zu einem Partner-Brief hoch. Prüft vor dem Speichern die Dateigröße (max. 50 MB) und die zusammengeführte Seitenzahl (max. 30 Seiten inkl. Brief und übriger Anhänge). Gedruckt wird nur A4 hochkant: eine andere Seite (US Letter, A5, quer) setzt FrankKi verkleinert auf A4, und die Antwort nennt sie in pageFormatNote. EN: Uploads a PDF as an attachment to a partner letter. Before saving, it checks the file size (max. 50 MB) and the merged page count (max. 30 pages including the letter and other attachments). Printing is A4 portrait only: FrankKi shrinks any other page (US Letter, A5, landscape) onto A4, and the answer names it in pageFormatNote.

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": {
      "letterId": "<letterId>"
    },
    "name": "attachment_upload_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
pdfUrlNoÖffentliche URL des PDF (Alternative zu pdfBase64). EN: Public URL of the PDF (alternative to pdfBase64).
letterIdYes
positionNo
pdfBase64NoPDF als Base64 (Alternative zu pdfUrl). EN: PDF as Base64 (alternative to pdfUrl).
reasoningNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, destructive=false, openWorld=true) by disclosing pre-save validation rules (50 MB, 30 merged pages), the A4-portrait normalization with automatic shrinking of US Letter/A5/landscape, and the response field pageFormatNote that reports it. That is exactly the kind of side-effect and transformation detail an agent needs before invoking a write tool.

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?

Content is front-loaded correctly (purpose, then limits, then print behavior), but the entire text is duplicated verbatim in German and English, so roughly half the tokens are redundant for any given reader. The underlying German text is itself economical.

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 no output schema, the description does name pageFormatNote, which is helpful, but it omits what happens when validation fails (error vs silent rejection), what title defaults to, what position means, and whether reasoning is required. For a mutating 6-parameter tool that is a meaningful gap.

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

Parameters2/5

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

Schema description coverage is only 33%: pdfUrl and pdfBase64 are documented in the schema, but letterId, title, position and reasoning are silent everywhere. The description compensates for none of this — it mentions no input parameter at all, and only references the pageFormatNote output field.

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: uploads a PDF as an attachment to a partner letter. The scope is unambiguous and clearly distinct from attachment_upload_image or letter_upload_pdf, though those siblings are never named, so the agent must infer the distinction from the resource noun.

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?

The context (attach a PDF to an existing partner letter, identified by letterId) is implied, and the pdfUrl vs pdfBase64 choice is documented only in the schema. There is no explicit 'use this instead of X when Y' guidance among the many attachment/upload siblings.

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.