Skip to main content
Glama
Sign In
gdb-mcp

gdb-mcp

by datobena
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gdb_command

Execute raw GDB commands within a live debugging session and retrieve the output to inspect program state, set breakpoints, or step through code.

Instructions

Execute a raw gdb command within a session and return the output.

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": {
      "session_id": "<session_id>",
      "command": "<command>"
    },
    "name": "gdb_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes
commandYes
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It fails to mention that commands may modify gdb state or have side effects, and does not explain timeout behavior, error handling, or session lock considerations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no extraneous information, which is appropriate for its brevity. However, it could incorporate more detail without becoming overly verbose, such as noting that commands are blocking or that the session must exist.

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?

Given the absence of an output schema, annotations, and parameter descriptions, the description is insufficient. It does not clarify the return format, error conditions, or the need for an active session, leaving the agent underinformed for correct invocation.

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?

Schema description coverage is 0%, meaning no parameter descriptions are provided in the schema. The tool description does not add meaning beyond parameter names; e.g., 'command' is described only as 'raw gdb command', which adds little semantic value. 'session_id' and 'timeout_seconds' lack any additional context.

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 clearly states the verb 'execute', the resource 'raw gdb command within a session', and the output 'return the output'. It is concise and unambiguous, but does not differentiate from the sibling tool 'batch_commands' which may perform similar command execution.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'batch_commands' or 'start_binary'. It does not mention prerequisites, such as requiring an active session, nor does it advise against use cases.

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