crash-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRASH_NO_COLOR | No | Disable colored console output | false |
| MAX_HISTORY_SIZE | No | Maximum steps to retain in history | 100 |
| CRASH_STRICT_MODE | No | Enable strict validation (requires specific prefixes) | false |
| CRASH_OUTPUT_FORMAT | No | Output format: console, json, markdown | console |
| CRASH_ENABLE_SESSIONS | No | Enable session management | false |
| CRASH_SESSION_TIMEOUT | No | Session timeout in minutes | 60 |
| CRASH_MAX_BRANCH_DEPTH | No | Maximum branch nesting depth | 5 |
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 | {} |
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 confusion or overlap. The tool's purpose of recording structured reasoning steps is clearly distinct and unambiguous.
Since there is only one tool, there are no naming inconsistencies to evaluate. The name 'crash' is somewhat unconventional but does not conflict with any other tools.
A single tool feels thin for a server, especially one named 'crash-mcp' which hints at broader scope. However, for the narrow purpose of logging reasoning steps, one tool could be sufficient, making it borderline.
The tool covers the full lifecycle of recording a reasoning step, including parameters for branching, revising, confidence, and final-step indication. It lacks explicit retrieval or management capabilities, but the domain is narrow enough that the tool is effectively complete.