Skip to main content
Glama

Vorlage abrufen

template_get
Read-only

Liefert eine einzelne Vorlage mit Betreff- und Inhaltsvorlage, den Merge-Feldern und der empfohlenen Freigabe-Voreinstellung. Eine Blockvorlage liefert zusätzlich blocksTemplate und styleDefs; kopiert und angepasst speichert template_save sie als eigenen Entwurf. Die Gestaltungskette beginnt hier: template_get auf einer kuratierten Standardvorlage (template_list markiert sie mit curated: true), Änderungen an blocksTemplate, letter_preview rendert den Stand, template_save speichert ihn, template_preview zeigt die gespeicherte Version, template_release gibt sie frei. Mit versionId und dem Scope template:write lässt sich auch eine bestimmte Entwurfsversion lesen. Nächster Schritt: template_apply_with_merge_fields füllt die Platzhalter mit Werten. EN: Returns a single template with subject and content template, the merge fields and the recommended approval default. A block template also returns blocksTemplate and styleDefs; once copied and modified, template_save stores it as an own draft. The crafting chain starts here: template_get on a curated standard template (template_list marks them with curated: true), edits to blocksTemplate, letter_preview renders the state, template_save stores it, template_preview shows the stored version, template_release releases it. With versionId and the template:write scope a specific draft version can be read too. Next step: template_apply_with_merge_fields fills the placeholders with values.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasoningNo
versionIdNoOptional: eine bestimmte Version, auch ein Entwurf. Braucht zusätzlich den Scope template:write. Ohne Angabe kommt die freigegebene Version. EN: Optional: one specific version, including a draft. Also requires the template:write scope. If omitted, the released version is returned.
templateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / versionId / description
      Previous value: -"Optional: eine bestimmte Version lesen, auch einen Entwurf. Braucht zusätzlich den Scope template:write. Ohne Angabe wird die freigegebene Version gelesen. EN: Optional: read one specific version, including a draft. Additionally requires the template:write scope. If omitted, the released version is read."New value: +"Optional: eine bestimmte Version, auch ein Entwurf. Braucht zusätzlich den Scope template:write. Ohne Angabe kommt die freigegebene Version. EN: Optional: one specific version, including a draft. Also requires the template:write scope. If omitted, the released version is returned."
  2. Changed1 schema field changed
    • changedInput schema / properties / versionId / description
      Previous value: -"Optional: eine bestimmte Version lesen, auch einen Entwurf. Braucht zusaetzlich den Scope template:write. Ohne Angabe wird die freigegebene Version gelesen. EN: Optional: read one specific version, including a draft. Additionally requires the template:write scope. If omitted, the released version is read."New value: +"Optional: eine bestimmte Version lesen, auch einen Entwurf. Braucht zusätzlich den Scope template:write. Ohne Angabe wird die freigegebene Version gelesen. EN: Optional: read one specific version, including a draft. Additionally requires the template:write scope. If omitted, the released version is read."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds useful behavioral context: what fields are returned, that block templates include blocksTemplate/styleDefs, and that reading a specific draft version requires the template:write scope.

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 core purpose is front-loaded, and the workflow details are logically ordered. However, the description repeats the entire content in German and English, making it substantially longer than necessary, and several workflow sentences could be tightened.

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?

With no output schema, the description appropriately explains the main return fields and the block-template variant. It also covers the important versionId scope behavior. Remaining gaps are mainly around templateId/reasoning semantics, which are separate parameter concerns.

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%, and the description does not compensate for templateId or reasoning. It mentions versionId's draft-reading behavior, but that largely repeats the schema description for versionId, and templateId is only implied through the curated-template workflow context.

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 states a specific verb and resource: it returns a single template with subject/content template, merge fields, and recommended approval default. It also distinguishes block templates by noting they additionally return blocksTemplate and styleDefs, which helps separate this tool from generic list/preview siblings.

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 workflow context: template_get starts the crafting chain on a curated standard template, followed by edits, letter_preview, template_save, template_preview, and template_release. It also names template_apply_with_merge_fields as the next step and explains the versionId draft-reading use case, though it does not explicitly state when not to use this versus alternatives.

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.