Skip to main content
Glama
the-real-talk

the-real-talk

rename_variable_collection

Rename a variable collection by ID or exact name without changing any variables or values.

Instructions

Rename a variable collection (designated by ID or exact name). Variables and their values are not touched.

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>",
      "name": "<name>"
    },
    "name": "rename_variable_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNew name
collectionYesID or exact name of the collection

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden alone. It usefully discloses the non-destructive scope (contents are untouched), but omits what happens on a name collision or duplicate name, and whether the operation fails or overwrites.

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?

Two short sentences, zero filler, with the target-identification detail front-loaded. It is close to optimal for a simple two-parameter mutation.

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 low-complexity, fully documented two-parameter tool with no output schema, this covers the essentials and preempts the main confusion (that renaming a collection changes its variables). Only collision/duplicate-name behavior is missing.

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 both parameters are already documented. The phrase "designated by ID or exact name" restates the schema's own wording without adding resolution rules or precedence when both forms could match.

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 variable collection") plus how the target is identified, which cleanly separates it from rename_variable, rename_variable_mode and rename_node. It stops short of naming a sibling alternative for contrast, so it lands at 4 rather than 5.

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?

Usage is implied by the resource naming: use it when the collection label itself must change. The clause "Variables and their values are not touched" implicitly routes agents away from variable-level renaming, but no explicit when/when-not or prerequisite guidance is given.

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