cyberrescue
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| stream_container_logsA | Fetch stdout/stderr logs from a Docker container by ID or name. |
| inspect_memory_dumpA | Return live memory and CPU stats, plus top processes, for a container. |
| execute_isolated_scriptA | Run a shell command string inside a container via |
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 3 tools
Each tool has a distinct purpose: running commands, inspecting memory/CPU, and fetching logs. There is no overlap, making it easy for an agent to differentiate and select the appropriate tool.
All tool names use snake_case and follow a verb_noun pattern, though the noun phrases vary in structure (e.g., 'isolated_script' vs 'memory_dump'). This is mostly consistent and readable.
Three tools is slightly minimal but appropriate for a focused container debugging/rescue server. The tools cover execution, resource inspection, and logs, which are core needs.
The server covers essential container debugging actions but lacks listing containers, file copying, or lifecycle management. This may limit its usefulness in broader rescue scenarios.