Skip to main content
Glama

Update topic

update_topic
Destructive

Rename or describe a topic.

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

Input Schema

NameRequiredDescriptionDefault
idYesTopic id
nameNoTopic name
descriptionNoWhat the topic covers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"What the topic covers"
    • addedInput schema / properties / name / description
      Added value: +"Topic 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, which is surprising for a rename and warrants explanation the description never gives. It also doesn't say whether omitted fields are preserved (patch) or cleared (replace), nor that topics are shared across contacts.

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 sentence with zero filler, and the mutating verbs are front-loaded. It is efficient, though five words is arguably too terse for a destructive three-parameter mutation.

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 write tool with no output schema, the description leaves the key questions unanswered: replace-vs-merge semantics, effect on contacts already assigned to the topic, and why the operation is flagged destructive. Schema richness covers parameters but not behavior.

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 the schema documents id, name, and description including maxLengths. The description only restates the rename/describe mapping, adding no format or constraint detail beyond the schema; baseline 3 applies.

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?

"Rename or describe a topic" gives a specific verb pair plus the resource, and the two verbs map cleanly onto the two mutable fields. It implicitly separates the tool from create_topic/delete_topic/get_topic, but never names them or states the boundary explicitly.

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_topic, get_topic, or the set_contact_topic/get_contact_topics pair. An agent must infer that this is the mutation path for an existing topic from the name alone.

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.