Skip to main content
Glama

FrankKi

by app.frankki
OverviewDiscussionsAdmin

Gespeicherte Vorlage ansehen

template_preview
Read-only

Rendert eine GESPEICHERTE Vorlage mit Beispielwerten und liefert Inline-PNGs, PDF-Link und designRender. designId oder ein ungespeichertes design bestimmen das Briefpapier; für eigenständige Formulare documentMode: "form" setzen. Die Vorschau bleibt kostenfrei und rein zum Ansehen. Für ein blocks-Layout, das erst im Entstehen ist, nimm letter_preview. Zum Persistieren einer fertigen Version template_save aufrufen. Falls das Tool clientseitig entfernt wurde, in der Tool-Suche exakt nach dem technischen Namen template_save suchen. EN: Renders a STORED template with sample values and returns inline PNGs, PDF link and designRender. designId or an unsaved design selects the stationery; set documentMode: "form" for standalone forms. The preview stays free of charge and is purely for looking at. Use letter_preview for a blocks layout that is still in the making. Call template_save to persist a finished version. If the client unloaded that tool, search for the exact technical name template_save.

Input Schema

NameRequiredDescriptionDefault
pagesNoWie viele Seiten als Bild zurückkommen. Standard 1, Maximum 3. EN: How many pages come back as images. Default 1, maximum 3.
designNoUngespeichertes Briefdesign nur für diese Vorschau. Für Formulare documentMode: "form" setzen. EN: Unsaved letter design for this preview only. Set documentMode: "form" for forms.
designIdNoGespeichertes Briefdesign für diese Vorlagenvorschau. EN: Saved letter design for this template preview.
reasoningNo
versionIdNoExakte Vorlagenversion, die geprüft werden soll. Ohne Angabe gilt die freigegebene Version, danach der neueste Entwurf. EN: Exact template version to inspect. If omitted, the released version is used, then the newest draft.
templateIdYesId der Vorlage aus template_list / template_get. EN: The template ID from template_list / template_get.
designVersionIdNoExakte unveränderliche Briefkopf-Version für diese Vorschau. EN: Exact immutable letterhead version for this preview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / design / description
      Previous value: -"Ungespeichertes Briefdesign nur fuer diese Vorschau. Fuer Formulare documentMode: \"form\" setzen. EN: Unsaved letter design for this preview only. Set documentMode: \"form\" for forms."New value: +"Ungespeichertes Briefdesign nur für diese Vorschau. Für Formulare documentMode: \"form\" setzen. EN: Unsaved letter design for this preview only. Set documentMode: \"form\" for forms."
    • changedInput schema / properties / designId / description
      Previous value: -"Gespeichertes Briefdesign fuer diese Vorlagenvorschau. EN: Saved letter design for this template preview."New value: +"Gespeichertes Briefdesign für diese Vorlagenvorschau. EN: Saved letter design for this template preview."
    • changedInput schema / properties / pages / description
      Previous value: -"Wie viele Seiten als Bild zurueckkommen. Standard 1, Maximum 3. EN: How many pages come back as images. Default 1, maximum 3."New value: +"Wie viele Seiten als Bild zurückkommen. Standard 1, Maximum 3. EN: How many pages come back as images. Default 1, maximum 3."
    • changedInput schema / properties / versionId / description
      Previous value: -"Exakte Vorlagenversion, die geprueft werden soll. Ohne Angabe gilt die freigegebene Version, danach der neueste Entwurf. EN: Exact template version to inspect. If omitted, the released version is used, then the newest draft."New value: +"Exakte Vorlagenversion, die geprüft werden soll. Ohne Angabe gilt die freigegebene Version, danach der neueste Entwurf. EN: Exact template version to inspect. If omitted, the released version is used, then the newest draft."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/destructive=false/openWorld=false, but the description adds real behavioral context: the preview is free of charge, is purely for viewing, and what it returns (inline PNGs, PDF link, designRender). It still omits auth prerequisites or rate limits, so it is not fully exhaustive.

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 and well ordered, but the entire description is duplicated in German and English, roughly doubling the length. The trailing sentence about searching for the technical name template_save is confusing noise that costs space without helping selection.

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?

For a 7-parameter, nested-schema tool with no output schema, the description covers purpose, alternatives, and the key parameter interactions, and it names the return artifacts. Remaining omissions are minor given that the structured schema carries most parameter detail.

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 86%, so the baseline is 3, but the description adds genuine meaning: how designId versus an unsaved design selects the stationery and that documentMode must be "form" for standalone forms. These relationships go beyond the field-level text.

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+resource+scope: renders a STORED template with sample values. It also enumerates the outputs (inline PNGs, PDF link, designRender) and explicitly contrasts with letter_preview and template_save, so an agent can distinguish it from siblings without opening any schema.

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?

Explicitly routes the agent: use letter_preview for a blocks layout still in progress, call template_save to persist a finished version, and set documentMode: "form" for standalone forms. It names both alternatives and the condition that selects each.

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