Skip to main content
Glama

removeBreakpoint

Remove a breakpoint by specifying the debug session and breakpoint ID.

Instructions

Remove a breakpoint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesID of the debug session
breakpointIdYesID of the breakpoint to remove

Implementation Reference

  • The handler function that executes the removeBreakpoint tool logic. It extracts breakpointId from args, sends a ClearBreakpoint command to the Delve session, removes the breakpoint from the session's breakpoints map, and returns a confirmation message.
    case "removeBreakpoint": {
      const { breakpointId } = args;
      await sendDelveCommand(session, "ClearBreakpoint", { id: breakpointId });
      session.breakpoints.delete(breakpointId);
    
      return {
        content: [{
          type: "text",
          text: `Removed breakpoint ${breakpointId}`
        }]
      };
    }
  • Tool registration schema for removeBreakpoint, defining its name, description, and inputSchema with sessionId (string) and breakpointId (number) as required properties.
      name: "removeBreakpoint",
      description: "Remove a breakpoint",
      inputSchema: {
        type: "object",
        properties: {
          sessionId: {
            type: "string",
            description: "ID of the debug session"
          },
          breakpointId: {
            type: "number",
            description: "ID of the breakpoint to remove"
          }
        },
        required: ["sessionId", "breakpointId"]
      }
    },
  • src/server.ts:411-412 (registration)
    The request handler routing: 'removeBreakpoint' is listed as a control command and dispatched to handleControlCommands() in control.ts.
    if (["setBreakpoint", "removeBreakpoint", "continue", "next", "step", "stepout", "variables", "evaluate"].includes(name)) {
      return handleControlCommands(name, args);
  • The Breakpoint interface type used to type the breakpoint objects managed by the session. This is relevant because removeBreakpoint deletes entries from session.breakpoints (Map<number, Breakpoint>).
    export interface Breakpoint {
      id: number;
      file: string;
      line: number;
      condition?: string;
    }
  • The sendDelveCommand utility function used by the removeBreakpoint handler to send the ClearBreakpoint API command to the Delve debugger.
    export async function sendDelveCommand(session: DebugSession, command: string, args: any = {}): Promise<any> {
      const { stdout } = await exec(`curl -s -X POST http://localhost:${session.port}/api/v2/${command} -d '${JSON.stringify(args)}'`);
      return JSON.parse(stdout);
    }
Behavior2/5

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

With no annotations, the description lacks disclosure of side effects, required session state, or potential errors. Simply stating the action does not provide behavioral context beyond the basic operation.

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 concise sentence that directly states the purpose without fluff. It is front-loaded and efficient, though it could be slightly more informative.

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?

For a simple remove operation, the description lacks information on return values, error conditions, or post-removal behavior. With no output schema, some indication of what the agent can expect after invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% coverage with clear parameter descriptions. The description adds no additional meaning beyond what the schema already provides, earning a baseline score of 3.

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?

Description clearly states the action 'Remove a breakpoint' with a specific verb and resource. However, it does not explicitly distinguish from sibling tools like 'setBreakpoint', though the inverse relationship is implicitly clear.

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 on when to use this tool versus alternatives, such as when to remove vs. disable a breakpoint. The description assumes the agent knows the context.

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/dwisiswant0/delve-mcp'

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