Skip to main content
Glama

gdb_delete_breakpoint

Delete a breakpoint by its number from a GDB debugging session. List breakpoints first with gdb_list_breakpoints to find the number. Deleted breakpoints cannot be recovered. Requires session ID from gdb_start_session.

Instructions

Delete a breakpoint by its number. Use gdb_list_breakpoints to see breakpoint numbers. Once deleted, the breakpoint cannot be recovered. Requires session_id parameter (obtained from gdb_start_session).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesSession ID from gdb_start_session
numberYesBreakpoint number

Implementation Reference

  • Tool registration: gdb_delete_breakpoint is registered as an MCP tool with its description and input schema.
    Tool(
        name="gdb_delete_breakpoint",
        description=(
            "Delete a breakpoint by its number. "
            "Use gdb_list_breakpoints to see breakpoint numbers. "
            "Once deleted, the breakpoint cannot be recovered. "
            "Requires session_id parameter (obtained from gdb_start_session)."
        ),
        inputSchema=BreakpointNumberArgs.model_json_schema(),
    ),
  • Input schema definition: BreakpointNumberArgs defines the session_id and number parameters for gdb_delete_breakpoint.
    class BreakpointNumberArgs(BaseModel):
        session_id: int = Field(..., description="Session ID from gdb_start_session")
        number: int = Field(..., description="Breakpoint number")
  • Handler: Dispatches gdb_delete_breakpoint calls, parsing BreakpointNumberArgs and calling session.delete_breakpoint().
    elif name == "gdb_delete_breakpoint":
        del_bp_args: BreakpointNumberArgs = BreakpointNumberArgs(**arguments)
        result = session.delete_breakpoint(number=del_bp_args.number)
  • Core implementation: GDBSession.delete_breakpoint() sends the GDB/MI command '-break-delete {number}' and returns the result.
    def delete_breakpoint(self, number: int) -> dict[str, Any]:
        """
        Delete a breakpoint by its number.
    
        Args:
            number: Breakpoint number to delete
    
        Returns:
            Dict with status
        """
        result = self.execute_command(f"-break-delete {number}")
    
        if result["status"] == "error":
            return result
    
        return {"status": "success", "message": f"Breakpoint {number} deleted"}
Behavior4/5

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

With no annotations, the description must disclose behavioral traits. It states the action is irreversible ('cannot be recovered') and mentions the requirement for a session_id. This provides sufficient transparency for a simple deletion tool.

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 three sentences long, with the action first, followed by prerequisite and warning. Every sentence adds value, and there is no redundancy.

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

Completeness5/5

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

Given the tool's simplicity (no output schema, two straightforward parameters), the description covers purpose, prerequisite (session_id), how to get the number, and the irreversible nature. It is complete for an agent to use correctly.

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 input schema has 100% description coverage, but the description adds meaning by specifying that session_id comes from gdb_start_session and that number corresponds to breakpoint numbers from gdb_list_breakpoints. This adds context beyond the schema.

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 clearly states 'Delete a breakpoint by its number.' This is a specific verb ('delete') and resource ('breakpoint'), and it distinguishes the tool from siblings like gdb_disable_breakpoint (disable vs delete) and gdb_list_breakpoints (list vs delete).

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?

The description advises using gdb_list_breakpoints to see breakpoint numbers, indicating a prerequisite step. It also warns that the breakpoint cannot be recovered after deletion. It does not explicitly state when to avoid using this tool, but the context is adequate given the sibling set.

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/airfloats/gdb_mcp'

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