Skip to main content
Glama

Vorlage freigeben

template_release
Destructive

Gibt eine Entwurfsversion frei, sodass sie versendet werden kann; letzter Schritt der Gestaltungskette (template_get, anpassen, letter_preview, template_save, template_preview, template_release). template_preview zeigt dem Menschen eine Freigabekarte mit Freigeben-Knopf. template_release macht die Version sofort versandbereit, an dieser Karte vorbei, die die Person sonst selbst bestätigt; die Antwort vermerkt die Freigabe als Freigabe durch den Agenten. Über MCP geht das bei einem Konto mit genau einem aktiven Nutzer. Bei mehreren Nutzern gibt ein Mensch im Dashboard frei (Vier-Augen-Prinzip), und die Antwort enthält den Link dorthin. Danach füllt template_apply_with_merge_fields die Vorlage mit Werten, und letter_create_draft oder order_send verschickt das Ergebnis. EN: Releases a draft version so it can be sent; last step of the crafting chain (template_get, modify, letter_preview, template_save, template_preview, template_release). template_preview shows the human an approval card with a Release button. template_release makes the version sendable at once, bypassing that card, which the person otherwise confirms; the response records the release as released by the agent. Via MCP this works on an account with exactly one active user. With several users a human releases it in the dashboard (four-eyes principle), and the response contains the link. After that, template_apply_with_merge_fields fills the template with values, and letter_create_draft or order_send sends the result.

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>",
      "versionId": "<versionId>"
    },
    "name": "template_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasoningNo
versionIdYesDie freizugebende Entwurfsversion. EN: The draft version to release.
templateIdYes

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?

The description adds substantial behavior beyond the annotations: it discloses that the release bypasses the normal human approval step, that the response records the release as performed by the agent, and that multi-user accounts require dashboard approval under a four-eyes principle with a link returned. This is consistent with the destructiveHint=true annotation because it describes an immediate, agent-driven state change.

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 content is front-loaded and every substantive point about behavior, preconditions, and follow-on tools contributes to correct invocation. The main inefficiency is that the entire description is duplicated in German and English, which makes it longer than necessary despite the clarity.

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 complex mutation tool with no output schema, the description covers the important context: what the release does, the approval bypass, single-user versus multi-user behavior, the audit record, and the follow-on tools. An agent has enough information to decide whether to call it and what will happen when it does.

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 coverage is only 33%, so the description needs to compensate for undocumented parameters, but it does not. It mentions the draft version generically, yet does not explain templateId or the reasoning parameter, leaving most parameter meaning to be inferred.

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: releasing a draft version so it can be sent. It also distinguishes this tool from template_preview by explaining that template_release bypasses the human approval card, and it places the tool precisely at the end of the crafting chain.

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?

It explicitly says when to use this versus template_preview: template_preview shows a human approval card, while template_release makes the version immediately sendable without that confirmation. It also states the key precondition that this MCP path works only for an account with exactly one active user, and explains the multi-user alternative in the dashboard.

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.