Skip to main content
Glama
sbergeron42

gdb-multiarch-mcp

by sbergeron42

gdb_get_status

Check the current status of a GDB debugging session to monitor execution state and debugger activity for Nintendo Switch executables.

Instructions

Get the current status of the GDB session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `get_status` method inside the `GDBSession` class in `gdb_interface.py` provides the actual logic for retrieving the session status.
    def get_status(self) -> dict[str, Any]:
        """Get the current status of the GDB session."""
        return {
            "is_running": self.is_running,
            "target_loaded": self.target_loaded,
            "has_controller": self.controller is not None,
        }
  • The tool `gdb_get_status` is registered in `server.py` as part of the tool definitions.
    Tool(
        name="gdb_get_status",
        description="Get the current status of the GDB session.",
        inputSchema=NO_ARGS_SCHEMA,
    ),
  • The request handler in `server.py` dispatches the `gdb_get_status` tool to `session.get_status()`.
    elif name == "gdb_get_status":
        result = session.get_status()
Behavior2/5

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

No annotations are provided, so the description carries full burden. While 'Get' implies a read operation, the description fails to disclose what status values are returned, whether the call is idempotent, performance characteristics, or side effects. It states the action but not behavioral traits.

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

Conciseness4/5

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

The description is a single, efficient sentence with no redundant words. It is appropriately front-loaded with the verb. However, extreme brevity limits completeness given the lack of output schema.

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?

With no output schema provided, the description should explain what status information is returned (e.g., execution state, stop reason). It fails to compensate for the missing structured return value documentation, leaving the agent unaware of what data to expect.

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 has zero parameters (empty schema), which establishes a baseline score of 4 according to the evaluation rules. No parameter documentation is required.

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 a specific verb ('Get') and resource ('current status of the GDB session'), clearly distinguishing it from siblings like gdb_get_threads or gdb_get_registers which retrieve specific data rather than session state. However, it doesn't specify what 'status' means (e.g., running/stopped/connected).

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, or under what conditions it should be called (e.g., before/after execution commands). Given the numerous sibling tools for execution control (gdb_continue, gdb_step), explicit usage context is absent.

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