Skip to main content
Glama

cascade_rename

Rename a strategy cascade or change the question it answers without changing its key.

Instructions

Rename a cascade, or change the question it answers. Its key stays the same.

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": {
      "cascade": "<cascade>"
    },
    "name": "cascade_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
cascadeYes
questionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only that the key remains the same, without explaining permissions, reversibility, side effects, or what happens when optional fields are omitted or left empty.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences, front-loads the action, and adds the key invariant without any unnecessary wording. Every sentence contributes useful information.

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?

The tool is simple and has an output schema, so return values need not be explained. However, with no annotations and 0% schema description coverage, the definition leaves important invocation details unclear, including parameter optionality, defaults, and mutation safety.

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%, so the description must compensate for the bare schema. It implies that 'cascade' is the target, 'name' is the new name, and 'question' is the replacement question, but it does not explain required fields, empty-string defaults, or whether both name and question can be changed together.

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?

The description states a specific verb and resource: 'Rename a cascade, or change the question it answers.' It also clarifies that the cascade's key stays the same. It does not explicitly distinguish itself from siblings such as cascade_create, cascade_delete, or cascade_list, so it is clear but not fully differentiated.

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?

The description implies when to use the tool: when renaming a cascade or changing its question. However, it gives no explicit when-not guidance, prerequisites, or alternatives to use instead, leaving usage context only implied.

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