Skip to main content
Glama

gdb_list_sessions

List all active debugging sessions in GDB to manage and monitor running processes during program analysis.

Instructions

List all active GDB sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • server.py:96-102 (registration)
    MCP tool registration: The gdb_list_sessions function is decorated with @mcp.tool() and serves as the entry point. It calls _get_gdb_tools().list_sessions() to get the list of active sessions.
    @mcp.tool()
    def gdb_list_sessions() -> str:
        """List all active GDB sessions."""
        try:
            return _get_gdb_tools().list_sessions()
        except Exception as e:
            return f"Error: {str(e)}"
  • Handler implementation: The list_sessions() method in GDBTools class retrieves the session list from the session manager and formats it for display. Returns 'No active GDB sessions' if empty, otherwise lists all active session IDs.
    def list_sessions(self) -> str:
        sessions = self.sessionManager.list_sessions()
        if not sessions:
            return "No active GDB sessions"
        return "Active GDB sessions:\n" + "\n".join(f"- {sid}" for sid in sessions)
  • Session manager helper: The list_sessions() method in GDBSessionManager cleans up dead sessions first, then returns the list of active session IDs stored in the sessions dictionary.
    def list_sessions(self) -> list:
        self._cleanup_dead_sessions()
        return list(self.sessions.keys())
  • Interface definition: The abstract base class DebuggerTools defines the contract for list_sessions() method that returns a string representation of active debugging sessions.
    @abstractmethod
    def list_sessions(self) -> str:
        """List all active debugging sessions."""
        pass
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it lists sessions but doesn't specify what 'active' means, whether it requires authentication, if it's read-only or has side effects, or how results are returned. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence that states the core functionality without any wasted words. It's front-loaded with the main action and resource, making it immediately clear what the tool does. Every word earns its place.

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?

Given the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, with no annotations and multiple similar sibling tools, it should do more to clarify the GDB-specific context and behavioral aspects. The output schema helps, but the description lacks completeness for a tool in a debugger family with alternatives.

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 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter information, and it correctly doesn't mention any parameters. Baseline 4 is appropriate for zero-parameter tools when the schema coverage is complete.

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 clearly states the verb ('List') and resource ('all active GDB sessions'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'debugger_list_sessions' or 'lldb_list_sessions', which would require mentioning it's specifically for GDB debugger sessions.

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?

The description provides no guidance on when to use this tool versus alternatives like 'debugger_list_sessions' or 'lldb_list_sessions'. It doesn't mention prerequisites, context for when listing sessions is appropriate, or any exclusions. The agent must infer usage from the tool name alone.

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/smadi0x86/MDB-MCP'

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