Skip to main content
Glama
Sign In
gdbstub-mcp

gdbstub-mcp

by 0xmortuex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

debug_break

Set software or hardware breakpoints and read/write/access watchpoints to debug bare-metal kernels running in QEMU.

Instructions

Set a breakpoint or watchpoint.

location: 0x1234, symbol, symbol+0x10, or file.c:42. kind: "sw" (software breakpoint), "hw" (hardware breakpoint - use this before paging is enabled or for code that isn't loaded yet), or a watchpoint: "write", "read", "access" (length bytes, default one word).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "location": "<location>"
    },
    "name": "debug_break"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNosw
nameYes
lengthNo
locationYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the sw/hw/watchpoint semantics and the watchpoint length default, which is useful behavioral context. It does not say whether the breakpoint persists across continue/reset, whether it needs a prior connection, or what side effects setting one has on a running target.

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?

Compact and front-loaded: the action comes first, then per-parameter detail in a scannable list. Every sentence adds information; nothing is repetitive filler.

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?

For a 4-parameter mutation tool with no annotations and zero schema coverage, the description covers three parameters well, and the output schema handles return values. The unexplained `name` parameter is the main completeness hole, along with unstated connection prerequisites.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must supply meaning, and it does: it enumerates location formats (0x1234, symbol, symbol+0x10, file.c:42), defines each kind value, and explains length for watchpoints including the one-word default. The required `name` parameter is never mentioned, leaving a notable gap.

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?

Opens with a specific verb and resource: "Set a breakpoint or watchpoint." An agent can immediately distinguish this from debug_breakpoints (likely listing) or debug_delete. It stops short of naming any sibling explicitly, so it does not reach the differentiation bar for a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real conditional guidance for the hardware kind: "use this before paging is enabled or for code that isn't loaded yet." That is usage guidance for a parameter, not for choosing this tool over debug_breakpoints or debug_delete. No prerequisites (e.g., needing debug_connect first) or exclusions are stated.

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

Deploy Server

Other Tools