re-gdb
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 |
|---|---|
| check_gdbA | Return gdb version + whether GEF is configured. |
| start_sessionC | Open (or reuse) a GDB session. Optionally load a binary. |
| end_sessionC | Tear down a GDB session. |
| run_to_breakpointC | Set a breakpoint at target and run to it. |
| step_countC | Single-step count times, return register state after. |
| read_memoryC | Read count memory units at addr. |
| gef_heapC | GEF: heap chunks (glibc malloc bins). |
| gef_canaryD | GEF: stack canary check. |
| gef_registersC | GEF: registers (extended view). |
| gef_vmmapC | GEF: vmmap (mapped regions with perms). |
| gef_nearpcB | GEF: nearpc (look ahead N instructions from PC). |
| gef_pattern_createA | Create a cyclic pattern of length bytes (for offset-finding). |
| gef_pattern_offsetB | Find the offset of value in a cyclic pattern. |
| attach_pidC | Attach to a running process by PID. |
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 14 tools
Each tool targets a distinct GDB operation or GEF feature, with clear separation between session management, memory reading, stepping, breakpoints, and specific GEF utilities. No two tools have overlapping purposes.
Tool names follow a predictable pattern: core GDB operations use verb_noun (attach_pid, read_memory) while GEF-specific tools use the gef_ prefix followed by a noun (gef_heap, gef_registers). Within each subgroup, naming is consistent and intuitive.
14 tools is well-scoped for a GDB interface, covering essential debugger actions (attach, breakpoint, step, memory read) and key GEF features (heap, registers, vmmap, canary, pattern). Not too few nor overwhelming.
Covers core debugging operations but misses common tasks like memory write, expression evaluation, breakpoint deletion, continuing execution, and arbitrary command execution. These gaps may limit agent autonomy for complex reverse engineering workflows.