Skip to main content
Glama
Sign In
gdbstub-mcp

gdbstub-mcp

by 0xmortuex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

debug_interrupt

Halt a running QEMU target immediately to pause execution and regain debugger control, similar to Ctrl-C in GDB.

Instructions

Halt a running target immediately (like Ctrl-C in gdb).

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>"
    },
    "name": "debug_interrupt"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and leaves key behavior undisclosed: whether the interrupt is asynchronous, whether the process is killed or merely paused, whether breakpoint/session state survives, and whether execution can be resumed with debug_continue. "Immediately" is the only behavioral hint offered.

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?

One sentence, front-loaded with the action, and the parenthetical analogy adds real interpretive value rather than padding. Nothing extraneous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but for a state-changing control operation with no annotations and an undocumented parameter, the definition omits what an agent most needs: what "name" refers to and what the target's state becomes after the halt.

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

Parameters2/5

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

The single required parameter "name" has 0% schema description coverage, and the description does not say whether it identifies a session, a target, or a process. The whole semantic burden for the one argument is unaddressed.

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?

The description gives a specific verb and resource ("Halt a running target") plus a concrete analogy (Ctrl-C in gdb) that pins down the operation. It is distinguishable from siblings like debug_continue, debug_step, and debug_break by implication of interrupting an in-flight execution, though it never names those alternatives.

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?

Usage is only implied: "a running target" and "immediately" suggest it applies while execution is in progress, but there is no explicit when-to-use, when-not-to-use, or prerequisite (e.g., must be connected to a session). The gdb analogy does some of the work for an agent familiar with debuggers.

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