Skip to main content
Glama
the-real-talk

the-real-talk

rename_variable_mode

Renames a variable mode in a collection by ID or name, letting you update mode labels without recreating them.

Instructions

Rename a mode (ID or name) of a collection.

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": {
      "collection": "<collection>",
      "mode": "<mode>",
      "name": "<name>"
    },
    "name": "rename_variable_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
nameYes
collectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a mutation but never states required permissions, whether the rename is reversible, whether variable bindings tied to the mode are affected, or what happens on name collisions. This is a substantial gap for a write operation.

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 target front-loaded; nothing is padded. The ambiguity in the parenthetical is a precision problem rather than a verbosity problem.

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 three-parameter mutation tool with no annotations, no output schema, and a broken parameter schema, the description is far too thin. An agent cannot determine argument formats, side effects, or error conditions 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% and the schema itself is unhelpful: both 'mode' and 'name' are $refs to the 'collection' string definition, so their real meaning is opaque. The description only weakly hints that the collection may be identified by ID or name, and never explains that 'name' is the new name or what 'mode' should contain. It does not compensate for the coverage gap.

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: rename a mode belonging to a collection. The word 'mode' distinguishes it from the sibling rename_variable and rename_variable_collection tools. However, the parenthetical '(ID or name)' is ambiguous about which argument it qualifies, muddying an otherwise clear purpose.

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?

No guidance on when to use this tool versus alternatives such as rename_variable or rename_variable_collection. It also omits prerequisites, e.g. whether the mode must already exist or whether the collection must be unlocked. The only routing signal is the noun 'mode'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools