Skip to main content
Glama

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; eigenständige Formulare rendern mit documentMode: "form". Die Vorschau ist kostenfrei und rein zum Ansehen. Ein blocks-Layout, das erst entsteht, rendert letter_preview; eine fertige Version speichert template_save (technischer Tool-Name template_save). EN: Renders a STORED template with sample values and returns inline PNGs, PDF link and designRender. designId or an unsaved design selects the stationery; standalone forms render with documentMode: "form". The preview is free of charge and purely for looking at. letter_preview renders a blocks layout still in the making; template_save stores a finished version (technical tool name template_save).

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": {
      "templateId": "<templateId>"
    },
    "name": "template_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNoWie viele Seiten als Bild zurückkommen. Standard 1, Maximum 3. 0: nur PDF-Link. EN: How many pages come back as images. Default 1, maximum 3. 0: PDF link only.
designNoUngespeichertes Briefdesign nur für diese Vorschau. Formulare rendern mit documentMode: "form". EN: Unsaved letter design for this preview only. Forms render with documentMode: "form".
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. Changed1 schema field changed
    • changedInput schema / properties / design / description
      Previous 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."New value: +"Ungespeichertes Briefdesign nur für diese Vorschau. Formulare rendern mit documentMode: \"form\". EN: Unsaved letter design for this preview only. Forms render with documentMode: \"form\"."
  2. Changed2 schema fields changed
    • changedInput schema / properties / pages / description
      Previous value: -"Wie viele Seiten als Bild zurückkommen. 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. 0: nur PDF-Link. EN: How many pages come back as images. Default 1, maximum 3. 0: PDF link only."
    • changedInput schema / properties / pages / minimum
      Previous value: -1New value: +0
  3. 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."
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only and non-destructive, but with no output schema the description carries the burden of describing the return payload (inline PNGs, PDF link, designRender) and it does so. It also adds the cost characteristic (free) and the STORED-vs-unsaved distinction, though it does not address rate limits or page-count tradeoffs beyond what the schema's pages parameter already says.

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?

Purpose and output are front-loaded in the first clause, followed by the design selection rule, then the sibling routing. The bilingual DE/EN duplication doubles the length and phrases like 'technischer Tool-Name template_save' restate the obvious, but no sentence is logically redundant.

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 tool with a deeply nested design object and no output schema, the description covers the return shape, the design-vs-designId choice, and the form mode. It leaves the nested design sub-object entirely to the schema, which is acceptable at 86% coverage, so nothing essential for a correct call 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 86%, so the baseline is 3; the description goes further by explaining that designId or an unsaved design object selects the stationery and that documentMode: "form" switches rendering mode for standalone forms, which is the key semantic relationship between two parameters that the schema does not spell out.

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 with scope: renders a STORED template with sample values. It explicitly names what the output contains (inline PNGs, PDF link, designRender) and distinguishes itself from letter_preview (unsaved blocks layout) and template_save (persisting), so an agent can pick it without opening a 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?

Gives explicit routing rules: use letter_preview for a blocks layout still in the making, template_save to store a finished version, and documentMode: "form" for standalone forms. It also states the preview is free of charge and purely for viewing, which tells the agent there is no side effect risk in calling it liberally.

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.