Skip to main content
Glama

cascade_list

Lists available strategy cascades with each key, name, guiding question, and position count so you can choose the right one for listing or adding positions.

Instructions

The strategies (cascades) in this store: key, name, the question each answers, and how many positions it holds. Pass a key as cascade to list or add.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cascade_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the returned fields (a genuine transparency gain, even though an output schema exists) and the read-only nature is strongly implied by the listing framing, but it says nothing about ordering, pagination or size limits, behavior when the store is empty, or any permission requirements.

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 sentences, zero waste, with the resource and its contents front-loaded before the actionable follow-up about reusing keys. Nothing is repeated and nothing extraneous is included.

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 simple, zero-parameter read tool with an output schema, this is close to complete: it identifies the resource, summarizes the returned fields, and connects the output to sibling calls. The only missing piece an agent might want is whether results are ordered or bounded in size.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to document; the baseline for a 0-param tool is 4. The description does not add parameter meaning, but none is needed here.

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 names the resource concretely — 'the strategies (cascades) in this store' — and enumerates what each entry contains (key, name, the question it answers, position count), which makes the enumeration/listing intent unmistakable. It stops short of naming sibling tools like show or cascade_create as alternatives, so the differentiation is contextual rather than explicit.

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 second sentence gives useful follow-up direction: 'Pass a key as `cascade` to `list` or `add`', which tells the agent what to do with the returned keys. However, there is no guidance on when to call this versus cascade_create, cascade_rename, or show, and no statement of exclusions, so usage is implied rather than spelled out.

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