Skip to main content
Glama

FrankKi

by app.frankki
OverviewDiscussionsAdmin

Bild-Anhang hochladen

attachment_upload_image

Lädt ein Bild (PNG/JPEG) als Anhang zu einem Partner-Brief hoch. Das Bild wird serverseitig auf eine A4-PDF-Seite skaliert (optional gedreht) und wie ein PDF gespeichert. Prüft vor dem Speichern die zusammengeführte Seitenzahl (max. 30 Seiten). Die EXIF-Orientierung wird automatisch in die Pixel eingerechnet, ein Handyfoto steht also von selbst aufrecht. rotation wirkt zusätzlich dazu: lass es auf 0, außer du willst das Bild bewusst weiterdrehen. EN: Uploads an image (PNG/JPEG) as an attachment to a partner letter. The image is scaled to an A4 PDF page server-side (optionally rotated) and stored like a PDF. Before saving, it checks the merged page count (max. 30 pages). EXIF orientation is applied to the pixels automatically, so a phone photo is upright by itself. rotation applies on top of that: leave it at 0 unless you deliberately want to turn the image further.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
imageUrlNoÖffentliche URL des Bildes (Alternative zu imageBase64). EN: Public URL of the image (alternative to imageBase64).
letterIdYes
positionNo
rotationNoZusätzliche Drehung in Grad, im Uhrzeigersinn. Die EXIF-Orientierung des Bildes wird bereits automatisch in die Pixel eingerechnet, das Bild steht also von sich aus richtig. Dieser Wert dreht es danach ein zweites Mal. Für ein Handyfoto ist deshalb 0 richtig. EN: Additional clockwise rotation in degrees. The image's EXIF orientation is already baked into the pixels automatically, so the image is upright on its own. This value turns it a second time on top of that. For a phone photo, 0 is therefore the correct value.
reasoningNo
imageBase64NoBild als Base64 (Alternative zu imageUrl). EN: Image as Base64 (alternative to imageUrl).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the minimal annotations, the description discloses rich behavior: server-side scaling to A4 PDF, optional rotation, page-count validation (max 30), automatic EXIF orientation handling, and the fact that rotation applies on top of EXIF correction. It also clearly implies a persisted write operation, consistent with readOnlyHint=false.

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?

The description is front-loaded with the main action and format, then covers transformation, limits, and rotation. It is concise despite being bilingual; the English repetition adds length but also makes the content robust for mixed audiences. No filler or vague marketing language.

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?

The core operation and transformation rules are well covered, including the page-count limit and EXIF behavior. However, there is no description of the return value or result confirmation (no output schema), no explanation of the position/title/reasoning parameters, and no guidance on the precedence or mutual exclusivity of imageUrl versus imageBase64.

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 43%, so the description must compensate, but it only elaborates on rotation (mostly repeating the schema) and the accepted image formats. It does not explain title, letterId, position, reasoning, or how to choose between imageUrl and imageBase64. This leaves the majority of parameters under-documented.

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?

The description opens with a specific verb ('Lädt ... hoch'), a concrete resource ('ein Bild (PNG/JPEG) als Anhang zu einem Partner-Brief'), and states the server-side conversion to an A4 PDF page. This clearly separates it from sibling attachment_upload_pdf, since the input format and transformation are explicit.

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?

The description gives clear context: use this tool when you need to attach a PNG/JPEG image to a partner letter and have it converted to PDF. It does not explicitly name the sibling attachment_upload_pdf or state 'for PDFs use that tool instead,' but the image-only restriction and conversion behavior make the intended use evident.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FrankKi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources