Skip to main content
Glama
sbergeron42

gdb-multiarch-mcp

by sbergeron42

gdb_step

Execute the next instruction in the debugging session for Nintendo Switch executables to analyze code flow and identify issues.

Instructions

Step into the next instruction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `step` method in `GDBSession` class sends the `-exec-step` command to GDB, which implements the step-into logic.
    def step(self) -> dict[str, Any]:
        """
        Step into (single source line, 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-step")
  • The `gdb_step` tool is registered here with its description and input schema.
    Tool(
        name="gdb_step",
        description="Step into the next instruction.",
        inputSchema=NO_ARGS_SCHEMA,
    ),
  • The handler in the main server loop calls `session.step()` when the `gdb_step` tool is invoked.
    elif name == "gdb_step":
        result = session.step()
Behavior3/5

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

With no annotations provided, the description carries the full burden. While 'step into' describes the execution flow, it omits that this operation blocks until completion, mutates program state (registers/memory), and requires an active inferior process.

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?

Extremely concise at 5 words. Single sentence immediately conveys the operation without filler. Perfectly front-loaded for quick comprehension.

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?

Adequate for a zero-parameter tool with no output schema, but given the density of sibling debugging tools (28 total), the description should clarify blocking behavior and error conditions (e.g., requires active target) to aid tool selection.

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?

Zero parameters present. Per guidelines, 0 params = baseline 4. The schema requires no additional semantic explanation.

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?

Uses specific debugging terminology 'step into' plus resource 'instruction', clearly indicating this executes the next machine instruction and enters function calls. However, it does not explicitly contrast with sibling gdb_next to help users select the correct stepping behavior.

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?

Provides no guidance on when to use this versus gdb_next (step over), gdb_continue (resume execution), or gdb_call_function. No prerequisites or conditions are mentioned.

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