Skip to main content
Glama
workbackai

MCP NodeJS Debugger

by workbackai

delete_breakpoint

Remove a breakpoint from NodeJS debugging sessions by specifying its ID to control code execution flow.

Instructions

Deletes a specified breakpoint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
breakpointIdYesID of the breakpoint to remove

Implementation Reference

  • The main handler function that executes the delete_breakpoint tool logic: ensures debugger enabled, sends 'Debugger.removeBreakpoint' command to the inspector WebSocket, removes from local breakpoints tracking, and returns success/error message.
    async ({ breakpointId }) => {
      try {
        // Ensure debugger is enabled
        if (!inspector.debuggerEnabled) {
          await inspector.enableDebugger();
        }
        
        await inspector.send('Debugger.removeBreakpoint', {
          breakpointId: breakpointId
        });
        
        // Remove from our local tracking
        inspector.breakpoints.delete(breakpointId);
        
        return {
          content: [{
            type: "text",
            text: `Breakpoint ${breakpointId} removed`
          }]
        };
      } catch (err) {
        return {
          content: [{
            type: "text",
            text: `Error removing breakpoint: ${err.message}`
          }]
        };
      }
    }
  • Input schema definition using Zod for the breakpointId parameter.
    {
      breakpointId: z.string().describe("ID of the breakpoint to remove")
    },
  • Registration of the delete_breakpoint tool on the MCP server using server.tool, including name, description, schema, and handler.
    server.tool(
      "delete_breakpoint",
      "Deletes a specified breakpoint",
      {
        breakpointId: z.string().describe("ID of the breakpoint to remove")
      },
      async ({ breakpointId }) => {
        try {
          // Ensure debugger is enabled
          if (!inspector.debuggerEnabled) {
            await inspector.enableDebugger();
          }
          
          await inspector.send('Debugger.removeBreakpoint', {
            breakpointId: breakpointId
          });
          
          // Remove from our local tracking
          inspector.breakpoints.delete(breakpointId);
          
          return {
            content: [{
              type: "text",
              text: `Breakpoint ${breakpointId} removed`
            }]
          };
        } catch (err) {
          return {
            content: [{
              type: "text",
              text: `Error removing breakpoint: ${err.message}`
            }]
          };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Deletes' implies a destructive mutation, it doesn't specify whether this action is reversible, what permissions are required, or what happens upon success/failure. For a destructive tool with zero annotation coverage, this leaves critical behavioral traits unaddressed.

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 with zero wasted words. It's front-loaded with the core action and resource, making it immediately clear without unnecessary elaboration, perfectly balancing brevity and clarity.

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?

Given this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral risks, success/failure outcomes, or integration with sibling tools (e.g., using 'list_breakpoints' first). For its complexity level, more contextual information is needed to guide safe and effective use.

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?

Schema description coverage is 100%, with the single parameter 'breakpointId' fully documented in the schema as 'ID of the breakpoint to remove'. The description adds no additional semantic context beyond what the schema provides, so it meets the baseline for adequate but unenhanced parameter documentation.

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 action ('Deletes') and the resource ('a specified breakpoint'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'list_breakpoints' or other debugging tools, which would require explicit comparison to achieve a perfect score.

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. With sibling tools like 'list_breakpoints' and 'set_breakpoint' available, there's no indication of prerequisites (e.g., needing an existing breakpoint ID) or when deletion is appropriate versus other debugging operations.

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/workbackai/mcp-nodejs-debugger'

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