Skip to main content
Glama

Update template

update_template
Destructive

Rename or edit a template.

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": {
      "id": "<id>"
    },
    "name": "update_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTemplate id
bodyNoThe message text, with merge tags
nameNoTemplate name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"The message text, with merge tags"
    • addedInput schema / properties / name / description
      Added value: +"Template name"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description should add context such as the fact that supplying 'body' overwrites the existing message text, or that changes are not reversible. 'Rename or edit' adds nothing beyond the annotation profile and does not warn that this is a destructive mutation. No contradiction with annotations, however.

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?

A single short, front-loaded sentence with zero filler. It is efficient, though arguably undersized given the destructive semantics of the operation.

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?

For a destructive, non-idempotent mutation with no output schema, the description omits whether the update is full-replace or partial, what happens to fields not supplied, and any irreversibility warning. An agent could call it and inadvertently clobber template body content.

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 100%, so id, body and name are fully documented in the schema, and the description's 'rename or edit' only loosely maps to name and body. Baseline 3 is appropriate since the schema does the work and the description contributes nothing extra (e.g. merge-tag behavior).

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 ('Rename or edit') and resource ('a template'), and the two verbs map cleanly onto the name/body fields. It does not distinguish itself from siblings like create_template, delete_template or get_template beyond the obvious verb, but the core action is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus create_template (for new templates) or get_template (to inspect without modifying), and no prerequisites such as needing the template id first. The agent must infer usage entirely from the verb.

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.