Dynamic MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (e.g., DEBUG, INFO, WARNING, ERROR) | INFO |
| KERNEL_PATH | No | Path to kernel directory | /boot |
| CRASH_DUMP_PATH | No | Path to crash dump directory | /var/crash |
| CRASH_COMMAND_TIMEOUT | No | Command timeout in seconds | 120 |
| CRASH_SESSION_TIMEOUT | No | Session timeout in seconds | 180 |
| SUPPRESS_MCP_WARNINGS | No | Suppress MCP initialization warnings | true |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crash_commandB | Execute a command in the crash utility session |
| get_crash_infoB | Get information about the current crash dump and session |
| list_crash_dumpsA | List all available crash dumps |
| start_crash_sessionC | Start a new crash session with a specific dump |
| close_crash_sessionA | Close the current crash session |
| execute_bpftrace_scriptB | Execute a BPFtrace script for system tracing and analysis |
| get_bpftrace_infoA | Get information about BPFtrace availability and version |
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 7 tools
Each tool serves a distinct function: session lifecycle (start/close), execution (crash command, BPFtrace script), information retrieval (crash info, BPFtrace info), and listing dumps. No overlaps.
Most tools follow a consistent verb_noun pattern (e.g., close_crash_session, list_crash_dumps), but 'crash_command' breaks this pattern as a noun_verb, causing minor inconsistency.
With 7 tools, the set is well-scoped for crash dump analysis and BPFtrace scripting. Each tool justifies its presence without being excessive or insufficient.
Core operations like session management, command execution, and info retrieval are covered. Minor gaps exist (e.g., no tool for saving sessions or filtering dumps), but not critical for the domain.