Skip to main content
Glama
sbergeron42

gdb-multiarch-mcp

by sbergeron42

gdb_next

Step over to the next line in Nintendo Switch debugging sessions using gdb-multiarch with Yuzu or hardware GDB stubs.

Instructions

Step over to the next line.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `next` method implementation within `GDBSession` class, which sends the `-exec-next` GDB/MI command.
    def next(self) -> dict[str, Any]:
        """
        Step over (next source line, not entering functions).
    
        Waits for the step to complete before returning. The (gdb) prompt indicates
        GDB is ready for subsequent commands.
    
        Returns:
            Dict with status and execution result
        """
        return self.execute_command("-exec-next")
  • The tool handler logic in the server that dispatches the "gdb_next" request to `session.next()`.
    elif name == "gdb_next":
        result = session.next()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to specify whether the operation blocks until execution stops, what happens if the next line is never reached (infinite loop), or that this mutates execution state (advances PC). 'Step over' implies function calls are skipped but doesn't clarify error conditions.

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 single sentence is efficient and front-loaded, but given the rich sibling context (20+ related tools) and lack of annotations, it is undersized rather than appropriately concise. Additional sentences explaining the step-over vs step-into distinction would earn their place.

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?

Incomplete given the high complexity of the GDB tool family. Lacks distinction from 'gdb_step', lacks behavioral details expected for debugger control commands (blocking/async nature), and provides no return value documentation (though no output schema exists, the behavioral contract is undocumented).

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?

Input schema has zero parameters (empty object), so baseline 4 applies per evaluation rules. The description appropriately makes no mention of parameters since none exist.

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 uses the specific technical phrase 'Step over' which correctly identifies the debugger operation (advancing to next source line without entering functions). However, it does not explicitly distinguish this from the sibling 'gdb_step' tool, which performs 'step into' operations—a critical distinction for debugging workflows.

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 provided on when to choose this over 'gdb_step' (step into), 'gdb_continue' (run freely), or 'gdb_interrupt'. No prerequisites mentioned (e.g., requires active inferior process, valid source line info). The description states what it does but not when to use it.

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

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/sbergeron42/gdb-multiarch-mcp'

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