Skip to main content
Glama
signal-slot

MCP GDB Server

by signal-slot

gdb_examine

Analyze and display memory contents during debugging sessions by specifying an address, expression, and format (e.g., hex or instructions) with GDB session integration.

Instructions

Examine memory

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of units to display
expressionYesMemory address or expression
formatNoDisplay format (e.g., "x" for hex, "i" for instruction)
sessionIdYesGDB session ID

Implementation Reference

  • Core handler function for the 'gdb_examine' tool. It validates the session, constructs the GDB examine command 'x/{count}{format} {expression}', executes it, and formats the response.
    private async handleGdbExamine(args: any) {
      const { sessionId, expression, format = 'x', count = 1 } = args;
      
      if (!activeSessions.has(sessionId)) {
        return {
          content: [
            {
              type: 'text',
              text: `No active GDB session with ID: ${sessionId}`
            }
          ],
          isError: true
        };
      }
      
      const session = activeSessions.get(sessionId)!;
      
      try {
        // Format examine command: x/[count][format] [expression]
        const command = `x/${count}${format} ${expression}`;
        const output = await this.executeGdbCommand(session, command);
        
        return {
          content: [
            {
              type: 'text',
              text: `Examine ${expression} (format: ${format}, count: ${count}):\n\n${output}`
            }
          ]
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return {
          content: [
            {
              type: 'text',
              text: `Failed to examine memory: ${errorMessage}`
            }
          ],
          isError: true
        };
      }
  • Input schema definition for the gdb_examine tool, specifying required sessionId and expression, optional format and count.
    inputSchema: {
      type: 'object',
      properties: {
        sessionId: {
          type: 'string',
          description: 'GDB session ID'
        },
        expression: {
          type: 'string',
          description: 'Memory address or expression'
        },
        format: {
          type: 'string',
          description: 'Display format (e.g., "x" for hex, "i" for instruction)'
        },
        count: {
          type: 'number',
          description: 'Number of units to display'
        }
      },
      required: ['sessionId', 'expression']
  • src/index.ts:309-334 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining name, description, and inputSchema for gdb_examine.
    {
      name: 'gdb_examine',
      description: 'Examine memory',
      inputSchema: {
        type: 'object',
        properties: {
          sessionId: {
            type: 'string',
            description: 'GDB session ID'
          },
          expression: {
            type: 'string',
            description: 'Memory address or expression'
          },
          format: {
            type: 'string',
            description: 'Display format (e.g., "x" for hex, "i" for instruction)'
          },
          count: {
            type: 'number',
            description: 'Number of units to display'
          }
        },
        required: ['sessionId', 'expression']
      }
    },
  • src/index.ts:387-388 (registration)
    Dispatch registration in the CallToolRequestSchema switch statement, routing gdb_examine calls to the handler.
    case 'gdb_examine':
      return await this.handleGdbExamine(request.params.arguments);
  • Shared helper function that executes GDB commands over stdin/stdout and captures/parses the output, used by gdb_examine handler.
    private executeGdbCommand(session: GdbSession, command: string): Promise<string> {
      return new Promise<string>((resolve, reject) => {
        if (!session.ready) {
          reject(new Error('GDB session is not ready'));
          return;
        }
        
        // Write command to GDB's stdin
        if (session.process.stdin) {
          session.process.stdin.write(command + '\n');
        } else {
          reject(new Error('GDB stdin is not available'));
          return;
        }
        
        let output = '';
        let responseComplete = false;
        
        // Create a one-time event handler for GDB output
        const onLine = (line: string) => {
          output += line + '\n';
          
          // Check if this line indicates the end of the GDB response
          if (line.includes('(gdb)') || line.includes('^done') || line.includes('^error')) {
            responseComplete = true;
            
            // If we've received the complete response, resolve the promise
            if (responseComplete) {
              // Remove the listener to avoid memory leaks
              session.rl.removeListener('line', onLine);
              resolve(output);
            }
          }
        };
        
        // Add the line handler to the readline interface
        session.rl.on('line', onLine);
        
        // Set a timeout to prevent hanging
        const timeout = setTimeout(() => {
          session.rl.removeListener('line', onLine);
          reject(new Error('GDB command timed out'));
        }, 10000); // 10 second timeout
        
        // Handle GDB errors
        const errorHandler = (data: Buffer) => {
          const errorText = data.toString();
          output += `[stderr] ${errorText}\n`;
        };
        
        // Add error handler
        if (session.process.stderr) {
          session.process.stderr.once('data', errorHandler);
        }
        
        // Clean up event handlers when the timeout expires
        timeout.unref();
      });
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states 'Examine memory' without disclosing behavioral traits like read-only nature, potential side effects, error conditions, or output format. It fails to provide necessary context for safe and effective use.

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?

The description is extremely concise with just two words, front-loaded and zero waste. Every word earns its place, though this conciseness contributes to gaps in other dimensions.

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 complexity of a debugging tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'examine' returns, how it behaves, or its role among siblings, leaving significant gaps for an AI agent.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema documents all parameters well. The description adds no meaning beyond the schema, as it doesn't explain parameter interactions or usage examples. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Examine memory' states a clear verb ('examine') and resource ('memory'), but it's vague about scope and doesn't distinguish from siblings like gdb_print or gdb_info_registers. It lacks specificity about what 'examine' entails compared to similar tools.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context, or exclusions, leaving the agent with no usage direction beyond the basic purpose.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/signal-slot/mcp-gdb'

If you have feedback or need assistance with the MCP directory API, please join our Discord server