Skip to main content
Glama

cascade_delete

Delete a cascade while preserving its positions, decisions, and evidence as unassigned positions listed under cascade "-".

Instructions

Delete a cascade. Its positions are kept, with their decisions and evidence, as unassigned positions (list with cascade "-").

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

Input Schema

NameRequiredDescriptionDefault
cascadeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations to lean on, the description steps up by disclosing the key side effect: positions, their decisions, and evidence are retained and become unassigned, discoverable via cascade "-". That is genuinely valuable behavior beyond the schema. It stops short of saying whether the cascade itself is unrecoverable or what happens to child objects.

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?

Two short sentences, no filler, with the operation front-loaded and the consequence immediately following. Nothing is redundant or padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the destructive side effect is explained, which covers the essentials for a one-parameter tool. Gaps remain around the parameter's format/identity and the irreversibility of the delete, which matter for a mutation call with no annotations.

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% for the single required parameter, so the description carries the burden, yet it never says whether "cascade" is a name, slug, or ID. The only hint is the quoted "-" sentinel used in list output, which is useful but does not define the input format.

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 ("Delete a cascade") and immediately adds the outcome, so the agent knows exactly what operation this is. It doesn't explicitly contrast with siblings such as cascade_rename or list, but the delete verb is distinctive enough among the named siblings.

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 rather than stated: the note that positions survive as unassigned positions signals this is the non-destructive-to-content option, which lets an agent infer when to prefer it. There is no explicit when-to-use, when-not-to-use, or prerequisite (permissions, confirmation) guidance.

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