Skip to main content
Glama

Vorlagenfreigabe auf der Karte entscheiden

template_decide_app
Destructive

Nur für die interaktive Vorlagen-Karte: gibt die angezeigte Entwurfsversion frei oder verwirft sie, nachdem der Mensch auf der Karte gedrückt hat. Freigeben macht die Vorlage für Versand und Agenten sichtbar. EN: For the interactive template card only: releases or discards the displayed draft version after the human pressed the button on the card. Releasing makes the template visible to sending and to agents.

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>",
      "decision": "<decision>"
    },
    "name": "template_decide_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
decisionYes
versionIdYes
templateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description adds real context by explaining the downstream effect of 'release' (template becomes visible to sending and agents). However, the destructive half of the operation is left vague: nothing says what 'discard' does to the draft, whether it is irreversible, or what happens to an already-released version.

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 scope constraint is front-loaded, which is good, but the German text is fully duplicated in English, so the same content occupies twice the space. For a three-parameter tool the payload is bloated without adding new information in the second half.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, a destructive hint, and three required undocumented parameters, the description should say more: the consequence of discard, reversibility, and what the caller receives back are all missing. What it does say about the card context and release visibility is accurate and useful, but the destructive path stays under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description has to carry the load, and it only partially does: it maps 'decision' to release/discard and hints at versionId via 'angezeigte Entwurfsversion', but never explains why both templateId and versionId are required or how they relate, and adds no format or validation detail.

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?

States a specific pair of verbs (release/discard) and the exact resource (the displayed draft version of a template), plus the scope constraint 'nur für die interaktive Vorlagen-Karte'. This clearly separates it from the generic siblings template_release and template_draft_discard, even though those names are never cited explicitly.

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?

'Nur für die interaktive Vorlagen-Karte ... nachdem der Mensch auf der Karte gedrückt hat' gives an explicit when-to-use condition and implicitly excludes direct/programmatic use. It stops short of naming the alternative tools (template_release, template_draft_discard) an agent should pick when there is no card interaction.

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.