Skip to main content
Glama

cascade_create

Start a new, empty strategy cascade by name, optionally defining the question it answers, to begin organizing Playing to Win box positions.

Instructions

Start a new strategy (cascade) by name, with the question it answers (optional). It starts empty.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
questionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully states the resulting state ('It starts empty'), which tells the agent no content is copied or seeded, but it says nothing about name-uniqueness handling, error behavior, or persistence side effects of creating the object.

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?

One sentence plus a short fragment; the purpose is front-loaded and nothing is padded. The 'It starts empty' fragment earns its place by conveying initial state.

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, so return values need no explanation, and the two-parameter surface is small. Still, for a mutation tool with zero annotations, the description omits failure modes (duplicate name, invalid input) that an agent would want before calling it.

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 0%, so the description must supply parameter meaning. It does map both parameters ('by name' and 'the question it answers (optional)'), confirming the question is optional, but adds no format, length, or uniqueness constraints for either field.

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 ('Start a new strategy (cascade)') and disambiguates the product term 'cascade' as 'strategy', which is genuinely helpful against siblings like cascade_rename and cascade_delete. It doesn't explicitly name an alternative, so it falls just short of a 5.

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 when-to-use or when-not-to-use guidance, no prerequisites, and no reference to the sibling tools such as cascade_list or cascade_rename. The agent must infer that this is the entry point for creating a new cascade purely from the verb.

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