CRASH - Cascaded Reasoning with Adaptive Step Handling
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRASH_NO_COLOR | No | Disable colored output | false |
| MAX_HISTORY_SIZE | No | Maximum steps to retain | 100 |
| CRASH_STRICT_MODE | No | Enable legacy validation rules | false |
| CRASH_OUTPUT_FORMAT | No | Output display format | console |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crashA | Record a structured reasoning step for complex problem-solving. Use this tool to break down multi-step problems into trackable reasoning steps. Each step captures your current thinking, expected outcome, and planned next action. WHEN TO USE:
WORKFLOW:
Returns JSON summary with step count, completion status, and next action. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'crash' has a clearly defined purpose for structured reasoning steps, so an agent cannot misselect between tools.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'crash' follows a single, consistent pattern with no deviations or mixing of conventions to evaluate.
A single tool is too few for the server's purpose of 'Cascaded Reasoning with Adaptive Step Handling,' which implies a multi-step or complex workflow. While the tool is well-described, a single tool feels thin and incomplete for such a domain, limiting functionality and agent capabilities.
The tool set is severely incomplete for the stated purpose. Although the 'crash' tool supports recording reasoning steps, there are obvious gaps—such as tools for retrieving, updating, or analyzing recorded steps, or for managing the reasoning process (e.g., starting, pausing, or summarizing). This will likely cause agent failures in complex tasks.