Skip to main content
Glama
yup-21
by yup-21

run_crash_command

Execute crash utility commands to analyze Linux system crash dumps, including sys, bt, log, ps, files, vm, and kmem operations.

Instructions

Runs crash utility command (e.g., sys, bt, log, ps, files, vm, kmem).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYes
session_idNo
truncateNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for 'run_crash_command', registered via @mcp.tool() decorator. Retrieves the session, validates it, and delegates command execution to UnifiedSession.execute_command with 'crash:' prefix.
    @mcp.tool()
    def run_crash_command(command: str, session_id: Optional[str] = None, truncate: bool = True) -> str:
        """Runs crash utility command (e.g., sys, bt, log, ps, files, vm, kmem)."""
        target_id = session_id or last_session_id
        
        if not target_id:
            return "Error: No session specified and no active default session."
        
        if target_id not in sessions:
            return f"Error: Session ID {target_id} not found."
        
        session = sessions[target_id]
        if not session.is_active():
            del sessions[target_id]
            return "Error: Session is no longer active."
            
        try:
            return session.execute_command(f"crash:{command}", truncate=truncate)
        except Exception as e:
            return f"Error executing command: {str(e)}"
  • The @mcp.tool() decorator registers the run_crash_command function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool runs commands but lacks critical details: it doesn't specify if this is a read-only or destructive operation, what permissions are required, how output is handled (though an output schema exists), or any rate limits. The examples hint at functionality but don't clarify behavioral traits.

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?

The description is a single, efficient sentence that front-loads the core purpose and includes helpful examples. There is no wasted verbiage, making it appropriately sized and easy to parse.

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?

Given the tool's complexity (running system commands), lack of annotations, and 0% schema description coverage, the description is incomplete. It doesn't address safety, permissions, or parameter meanings beyond command examples. However, the existence of an output schema reduces the need to explain return values, providing some baseline adequacy.

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

Parameters2/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 compensate for undocumented parameters. It only mentions the 'command' parameter through examples (e.g., sys, bt), but provides no context for 'session_id' or 'truncate'. This leaves two of three parameters without semantic explanation, failing to adequately compensate for the low coverage.

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 clearly states the action ('Runs') and target ('crash utility command'), and provides specific examples of commands (sys, bt, log, ps, files, vm, kmem). This makes the purpose specific and understandable, though it doesn't explicitly differentiate from sibling tools like 'run_drgn_command'.

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?

The description provides no guidance on when to use this tool versus alternatives like 'run_drgn_command' or 'list_crash_dumps', nor does it mention prerequisites such as needing a session (implied by the session_id parameter). Usage is implied through examples but not explicitly stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yup-21/crash-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server