Skip to main content
Glama

Brief und Vorlage prüfen

letter_preview
Read-only

Brief und Entwurf als Bild pruefen, Formularvorschau rendern: komponiert wie einen echten Versand und liefert Inline-PNGs, PDF-Link, Seitenzahl, Preis und designRender mit dem tatsaechlichen documentMode, den gezeichneten Brief-Elementen und bodyStartMm. Die Vorschau bleibt kostenfrei und der Brief bleibt liegen. Der Brief kommt ueber letterId oder inline mit content ODER blocks. Bei letterId ist die eingebettete Karte die Vorschau für den Menschen. Nach ihrer Anzeige reicht im Chat eine kurze Bestätigung; PDF-Link und Brieftext gehören in reine Textansichten. Ein ungespeichertes design kann direkt mitgegeben werden und gilt nur für diese eine Vorschau. WICHTIG FUER FORMULARE: Selbstauskunft, Fragebogen, Zertifikat und andere eigenstaendige Formulare immer zuerst mit design: { "schemaVersion": 1, "documentMode": "form" } pruefen; genau dann entfallen Empfaengerblock, Datum und Betreff und der Inhalt beginnt bei 27 mm. Kompaktes blocks-Beispiel: {"blocks":[{"type":"heading","text":"Rechnung"},{"type":"table","columns":[{"key":"text","label":"Artikel","width":"grow"},{"key":"sum","label":"Summe","align":"right","format":"eur"}],"rows":[{"text":"Beratung","sum":32000}]},{"type":"totals","lines":[{"label":"Gesamt","amountCents":32000,"emphasis":true}]}]} Volle Referenz: frankki://blocks-guide. Beim Nachbau ist letter_preview PFLICHT: PNG Seite fuer Seite mit dem Original vergleichen. Weichen Seitenzahl oder wesentliche Geometrie ab, korrigiere blocks oder design und rufe letter_preview erneut auf; gespeichert wird erst, wenn beides passt. Wenn das Layout sitzt mit template_save als Entwurf sichern und danach template_release nutzen. EN: Preview letter and draft as images, render form preview: composes like a real send and returns inline PNGs, PDF link, page count, cost and designRender with the actual documentMode, rendered letter chrome and bodyStartMm. The preview stays free of charge and the letter stays put. Use letterId or inline content OR blocks. With letterId, the embedded card is the human preview. Once it appears, a short chat confirmation is enough; PDF links and letter text belong in text-only views. An unsaved design may be supplied directly and applies to this one preview only. IMPORTANT FOR FORMS: always preview self-declarations, questionnaires, certificates and other standalone forms first with design: { "schemaVersion": 1, "documentMode": "form" }; that is what drops recipient block, date and subject and starts content at 27 mm. Full reference: frankki://blocks-guide. For a rebuild, compare every PNG page against the original. If page count or major geometry differs, correct blocks or design and preview again; save once both match. Once matched, save with template_save, then use template_release.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pagesNoWie viele Seiten als Bild zurueckkommen. Standard 3, Maximum 8. Der PDF-Link enthaelt immer alle Seiten. EN: How many pages come back as images. Default 3, maximum 8. The PDF link always contains every page.
blocksNoStrukturierter Briefinhalt als typisierte Bloecke (Alternative zu content, nie beides). Limits: 200 Bloecke, 100 Zeilen/Tabelle, 20 Spalten, 2000 Zeichen/Zelle, 10 Bilder, 262144 Bytes. EN: structured letter content as typed blocks (alternative to content, never both). Jeder Block braucht type; erlaubte Typen: paragraph, heading, keyValue, checkboxRow, fillLine, table, totals, columns, box, image, spacer, pageBreak. Die vollstaendige Feldreferenz liegt in der MCP-Ressource frankki://blocks-guide. EN: every block needs type; read frankki://blocks-guide for the complete field reference.
designNoUngespeichertes Briefdesign nur fuer diese Vorschau. Hat Vorrang vor designId und erzeugt keinen Eintrag im Konto. Fuer eigenstaendige Formulare documentMode: "form" setzen. EN: Unsaved letter design for this preview only. Takes precedence over designId and creates no account entry. Set documentMode: "form" for standalone forms.
contentNoBrieftext als Fliesstext. Entweder content ODER blocks, nie beides. EN: letter body as plain text. Either content OR blocks, never both.
subjectNoBetreff. Ohne letterId erforderlich. EN: Subject. Required without a letterId.
designIdNoEin gespeichertes Briefdesign fuer diese Vorschau verwenden. EN: Use a saved letter design for this preview.
languageNo
letterIdNoEinen gespeicherten Entwurf in der Vorschau anzeigen. Alternativ den Brief inline angeben. EN: Preview a stored draft. Alternatively provide the letter inline.
reasoningNo
referenceNoWerte fuer diesen Brief (Vorgangsnummer, Ihr Zeichen, Kundennummer, QR-Parameter ...). Sie fuellen Infoblock und Barcode in der Vorschau. EN: Per-letter values (Vorgangsnummer, your reference, customer number, QR parameters ...). They fill the info block and barcode in the preview.
styleDefsNoBenannte Stile fuer das ganze Dokument (max. 24). Bloecke referenzieren sie ueber style. EN: named document styles (max 24); blocks reference them via style. Vollstaendige Stilfelder: frankki://blocks-guide. EN: complete style fields: frankki://blocks-guide.
resolutionNothumb (96 dpi, Standard, schnell und klein) oder full (150 dpi, zum Pruefen von Details). EN: thumb (96 dpi, default, fast and small) or full (150 dpi, for checking details).
senderProfileIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/destructiveHint=false, so the safety profile is covered; the description still adds substantial behavior: 'stays free of charge', 'the letter stays put' (no persistence), the unsaved design scoped to a single preview, the letterId embedded-card-as-human-preview convention, and the concrete effect of documentMode 'form' (drops recipient block, date, subject; content begins at 27 mm). This is real context beyond the annotations.

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?

The purpose is front-loaded and the workflow guidance is valuable, but the entire block is duplicated in German and English, roughly doubling the length for a single reader. The embedded blocks example is also inline rather than deferred to the referenced resource, adding bulk. Structurally sound but not tight.

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?

For a 13-parameter tool with no output schema and nested objects, the description covers the modes (letter vs form), the return payload (PNG pages, PDF link, page count, cost, designRender, bodyStartMm), and the save workflow. Nothing an agent needs to invoke it correctly appears to be 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 77%, so the schema already documents most parameters (baseline 3). The description adds meaning on top: 'content OR blocks, never both', the form-mode design payload, a worked blocks example, and pointers to frankki://blocks-guide for the full field reference. It usefully compensates for the parameters the schema leaves thin.

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 opening states a specific verb and resource: 'Preview letter and draft as images, render form preview', and lists concrete outputs (inline PNGs, PDF link, page count, cost, designRender). It does not, however, differentiate itself from the close siblings letter_design_preview and template_preview, which an agent must distinguish between. Purpose is clear but sibling routing is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use and alternatives: 'Use letterId or inline content OR blocks', the form-mode rule ('always preview ... with documentMode form'), the rebuild instruction ('compare every PNG page against the original ... correct blocks or design and preview again'), and the follow-up path (template_save then template_release). Almost nothing about when/where-not is left to inference.

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.