Skip to main content
Glama

Vorlage archivieren

template_archive
Destructive

Archiviert eine Vorlage. Sie verschwindet aus den Listen und aus dem Versand, bleibt aber erhalten. Der Inhalt bleibt vollständig erhalten, und ein erneuter Aufruf ist unschädlich. EN: Archives a template. It disappears from the lists and from sending but is kept. The content stays fully preserved and calling it again is harmless.

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

Input Schema

NameRequiredDescriptionDefault
reasoningNo
templateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the template vanishes from lists and from sending, content is fully preserved, and the call is idempotent. This meaningfully softens/nuances the destructiveHint=true flag by telling the agent the effect is a reversible soft-archive rather than data loss.

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?

Front-loaded with the action and effect, and each sentence is short. But the entire content is duplicated in German and English, roughly doubling length with no added information.

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 two-parameter mutation with no output schema, the description covers the essential effects (visibility, sending, retention, idempotency). The remaining gap is the undocumented 'reasoning' parameter and the absence of error conditions (e.g., what happens with an unknown or already-archived ID beyond 'harmless').

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% and the description never mentions either parameter. It does not say that templateId must be a UUID or what 'reasoning' is for (audit note?), so an agent gets no semantic guidance beyond the raw schema types.

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+resource ('Archiviert eine Vorlage') and immediately describes the observable effect: removal from lists and sending while the record is retained. That distinguishes it from template_get/template_list/template_release without naming them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies the use case (retire a template without destroying it) and notes that repeat invocation is harmless, which helps an agent decide it is safe to retry. However, no explicit 'use this instead of X' guidance toward template_release, template_draft_discard, or template_list, and no stated prerequisites.

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.