BYO Server
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 |
|---|---|
| connectA | Open a debug session to a connected probe. |
| disconnectA | Close the active debug session and release the probe. |
| get_board_infoA | Return the facts from the board config the session was opened with. |
| get_stateA | Return the current core run state (e.g. HALTED, RUNNING, RESET). |
| haltB | Halt the core. |
| resumeC | Resume execution of the core. |
| stepB | Single-step one instruction and return the new program counter. |
| resetA | Reset the target. |
| read_core_registerA | Read a core register by name (e.g. "pc", "sp", "r0", "xpsr"). Returns the value as a hex string. |
| write_core_registerB | Write a core register by name. |
| read_memoryA | Read a single value from memory. |
| read_memory_blockB | Read |
| read_symbol_u32B | Resolve |
| write_memoryA | Write a single value to memory. |
| set_breakpointC | Set a hardware/software breakpoint at |
| remove_breakpointB | Remove the breakpoint at |
| flash_firmwareA | Flash firmware through the shared target-control service layer. |
| read_serialA | Capture bounded UART output through the shared serial-resolution and UART services. |
| write_serialA | Write bounded UTF-8 text to the connected board UART. |
| unlock_recoverA | Run the shared recover/unlock path for the connected board. |
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 20 tools
Each tool has a clearly distinct purpose: connect/disconnect, flash, board info, state control, memory/register access, breakpoints, serial, symbol reading, and recovery. No overlap.
Most tools follow verb_noun pattern (e.g., flash_firmware, read_memory), with some simple verbs (connect, halt). 'unlock_recover' is slightly inconsistent, but overall patterns are clear.
20 tools for a debug probe server is reasonable. It covers core debug operations without being excessive, though some tools could potentially be combined.
The tool set covers all essential debug operations: connect, flash, state control, memory/register R/W, breakpoints, serial I/O, symbol reading, and recovery. Minor gaps like conditional breakpoints are acceptable.