Skip to main content
Glama
sbergeron42

gdb-multiarch-mcp

by sbergeron42

gdb_continue

Resume program execution in Nintendo Switch debugging until reaching the next breakpoint or program completion. Use when debugging is paused.

Instructions

Continue execution until next breakpoint or completion. Only use when program is PAUSED.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The continue_execution method in GDBSession sends the -exec-continue command to GDB, which resumes execution of the debugged program.
    def continue_execution(self) -> dict[str, Any]:
        """
        Continue execution of the program.
    
        Waits for the program to stop (at a breakpoint, signal, or exit) before
        returning. The (gdb) prompt indicates GDB is ready for subsequent commands.
    
        Returns:
            Dict with status and execution result
        """
        return self.execute_command("-exec-continue")
  • The 'gdb_continue' tool is defined here for the MCP server.
    Tool(
        name="gdb_continue",
        description="Continue execution until next breakpoint or completion. Only use when program is PAUSED.",
        inputSchema=NO_ARGS_SCHEMA,
    ),
  • The tool handler for 'gdb_continue' calls session.continue_execution().
    elif name == "gdb_continue":
        result = session.continue_execution()
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. It discloses the halting conditions (breakpoint/completion) and the paused-state requirement, but omits whether this operation blocks until completion, error handling, or state side-effects.

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?

Two sentences with zero waste: first defines the action, second states the critical precondition. Information is front-loaded and appropriately sized for the tool's simplicity.

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

Completeness4/5

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

Given zero parameters and no output schema, the description adequately covers the essential operational constraint (PAUSED prerequisite). For a simple control-flow tool among many siblings, this is sufficient, though noting blocking behavior would improve it.

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?

The tool accepts zero parameters (empty schema), which per guidelines establishes a baseline of 4. The description appropriately requires no parameter clarification.

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

Purpose5/5

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

The description uses a specific verb ('Continue') with clear scope ('until next breakpoint or completion'), clearly distinguishing this from sibling stepping tools like gdb_step or gdb_next.

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

Usage Guidelines4/5

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

Provides explicit precondition 'Only use when program is PAUSED' which constrains when-not to use it. However, it doesn't explicitly name alternatives (e.g., 'use gdb_step to advance line-by-line instead').

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