Skip to main content
Glama

remove_breakpoint

Removes a previously set breakpoint by specifying the session ID and the breakpoint ID obtained from list_breakpoints or set_breakpoint.

Instructions

Removes a previously set breakpoint. Use list_breakpoints to find breakpoint IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesID of the debugging session.
breakpoint_idYesID of the breakpoint to remove. Obtain this from set_breakpoint or list_breakpoints.

Implementation Reference

  • Session manager handler for removing a breakpoint. Validates the breakpoint exists, delegates to CDP client to remove it, and cleans up the internal breakpoints set.
    async removeBreakpoint(
      sessionId: string,
      breakpointId: string
    ): Promise<void> {
      const session = this.getSession(sessionId);
    
      if (!session.breakpoints.has(breakpointId)) {
        throw this.createError(
          ErrorCode.BREAKPOINT_NOT_FOUND,
          `Breakpoint ${breakpointId} not found`
        );
      }
    
      await session.cdpClient.removeBreakpoint(breakpointId);
      session.breakpoints.delete(breakpointId);
    }
  • Input schema registration for the 'remove_breakpoint' tool, defining session_id and breakpoint_id as required string parameters.
    {
      name: 'remove_breakpoint',
      description:
        'Removes a previously set breakpoint. Use list_breakpoints to find breakpoint IDs.',
      inputSchema: {
        type: 'object',
        properties: {
          session_id: {
            type: 'string',
            description: 'ID of the debugging session.',
          },
          breakpoint_id: {
            type: 'string',
            description:
              'ID of the breakpoint to remove. Obtain this from set_breakpoint or list_breakpoints.',
          },
        },
        required: ['session_id', 'breakpoint_id'],
      },
  • src/server.ts:583-610 (registration)
    Tool dispatching logic: parses input with Zod schema, calls sessionManager.removeBreakpoint, and returns success response.
    case 'remove_breakpoint': {
      const params = z
        .object({
          session_id: z.string(),
          breakpoint_id: z.string(),
        })
        .parse(args);
    
      await sessionManager.removeBreakpoint(
        params.session_id,
        params.breakpoint_id
      );
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                success: true,
                breakpoint_id: params.breakpoint_id,
              },
              null,
              2
            ),
          },
        ],
      };
  • Low-level CDP client method that sends the Debugger.removeBreakpoint command to Chrome DevTools Protocol.
    async removeBreakpoint(breakpointId: string): Promise<void> {
      this.ensureConnected();
      await this.client!.Debugger.removeBreakpoint({breakpointId});
    }
  • TypeScript type declaration for the CDP Debugger.removeBreakpoint method.
    removeBreakpoint(params: Protocol.Debugger.RemoveBreakpointRequest): Promise<void>;
    resume(params?: Protocol.Debugger.ResumeRequest): Promise<void>;
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It states removal of a breakpoint, which is adequate for a simple destructive action. However, it doesn't mention any side effects, permissions, or implications beyond the obvious.

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, brief sentence with a useful hint. It is front-loaded and contains no redundant information.

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, and 100% schema coverage, the description is complete. It tells what it does and how to get the required ID, fitting well with sibling debugger tools.

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% description coverage for both parameters. The description adds minimal value beyond the schema, only reinforcing the hint for breakpoint_id. Baseline is 3 for high schema coverage.

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 'Removes a previously set breakpoint,' using a specific verb and resource. It distinguishes from sibling tools like set_breakpoint and list_breakpoints.

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 provides a clear usage hint: 'Use list_breakpoints to find breakpoint IDs.' While it doesn't explicitly list when not to use or alternatives, it gives context for obtaining the required parameter.

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/johngrimes/mcp-js-debugger'

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