Skip to main content
Glama

Vorlagenstand für die Karte lesen

template_status_app
Read-only

Nur für die interaktive Vorlagen-Karte: liest den aktuellen Zustand einer Vorlagenversion, damit eine alte Karte den richtigen Endzustand zeigt. EN: For the interactive template card only: reads the current state of a template version so an old card renders the correct end state.

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

Input Schema

NameRequiredDescriptionDefault
versionIdNo
templateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful rationale that it exists so an old card renders the correct end state, but says nothing about how fresh that state is, caching, or what the returned state actually contains.

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 restriction is front-loaded, which is good, but the description is a full bilingual duplication of the same two sentences, roughly doubling length without adding information. The German portion also uses domain jargon ('Vorlagenstand') that does not map cleanly to the English phrasing.

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

Completeness2/5

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

There is no output schema, so the description should explain what a 'state' is (status values? release state? merge-field state?) and how versionId omission resolves, and it does neither. For a two-parameter, undocumented-schema tool with no return contract, an agent cannot call it confidently from this text alone.

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 0% for two UUID parameters, so the description must carry the meaning — and it only implies versionId via 'state of a template version'. It never explains the required templateId, nor what happens when the optional versionId is omitted (latest version? draft?), which is the key semantic decision for a caller.

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 verb and resource ('reads the current state of a template version') and adds a scope limiter ('interactive template card only'), which distinguishes it from the broader template_get. It does not explicitly contrast itself with template_get or template_diff_check, so the differentiation is only partial.

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 clause 'Nur für die interaktive Vorlagen-Karte' / 'For the interactive template card only' is an explicit when-to-use and when-not-to-use signal. It stops short of naming the alternative an agent should use outside that card context (e.g. template_get), leaving that step to inference.

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.