cascade
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_graphA | Create a DAG of subtasks to be executed by parallel CLI agent workers. Validates the graph and starts the live viewer, but does not execute anything. |
| start_executionA | Begin executing a graph. Non-blocking: marks ready nodes, spawns workers, and returns immediately. |
| wait_for_changeA | Block until any node in the graph changes state, or until the timeout elapses. On a change, returns the changed nodes, a full snapshot, and whether the graph is fully terminal. On a timeout, the snapshot is omitted since nothing moved. |
| get_graph_stateB | Get an immediate snapshot of a graph: per-node state, truncated results, and counts. |
| get_node_outputC | Get the full result and log tail for a single node. |
| cancel_executionA | Cancel a running graph: SIGTERM all running workers and mark them failed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool serves a clear, non-overlapping purpose: create_graph defines the DAG, start_execution begins running it, wait_for_change and get_graph_state provide different monitoring modes, get_node_output fetches detailed results, and cancel_execution stops execution. There is no confusion between them.
Tool names follow a mostly consistent verb-first pattern in snake_case (start_execution, create_graph, cancel_execution). The get_ prefix is used consistently for retrieval tools, but wait_for_change breaks the pattern slightly by combining a phrasal verb with a preposition. Overall naming is readable and predictable.
With 6 tools, the server is well-scoped for graph-based execution management. Each tool covers a distinct phase of the workflow without redundancy or bloat.
The tool surface covers the full execution lifecycle: create, start, monitor, inspect outputs, and cancel. A missing delete_graph or graph update operation is a minor gap, but not a dead end for the primary purpose of running and observing graphs.