Skip to main content
Glama

Update list

update_list
Destructive

Rename a list or change its description.

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

Input Schema

NameRequiredDescriptionDefault
idYesList id
nameNoList name
descriptionNoWhat the list is for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"What the list is for"
    • addedInput schema / properties / name / description
      Added value: +"List 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 declare destructiveHint=true and idempotentHint=false, which is notable for what looks like a simple rename, and the description never explains why — e.g. that setting a new description overwrites the existing text, or that the name may need to be unique. Beyond restating the mutable fields, it adds no behavioral context such as permission requirements, the effect of omitting both optional fields, or whether both can be changed in one call.

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 the action and the affected fields front-loaded; nothing is wasted. Its brevity borders on under-specification, but every word earns its place structurally.

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 mutation tool flagged destructive, with no output schema to explain the result, the description does not cover what is returned, what happens if neither optional field is provided, or what data can be lost. An agent would need to inspect the schema and still guess at the risky edge cases.

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', 'name', and 'description' are already documented structurally. The description names the two mutable fields but adds no semantics beyond that (no uniqueness or length implications), so the schema carries the load — baseline 3.

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 concrete verb and resource ('Rename a list or change its description') rather than restating the name, so the agent knows exactly which two fields can be modified. It does not distinguish itself from nearby siblings such as update_segment, update_topic, or create_list/delete_list, but the operation itself 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 explicit when-to-use guidance, no prerequisites, and no named alternatives. The agent must infer that this is the tool for modifying an existing list versus create_list for making one or delete_list for removing one.

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.