Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

remove_breakpoint

Removes a debugger breakpoint by its breakpointId from set_breakpoint, enabling you to clean up or adjust breakpoints during Electron debugging sessions.

Instructions

Debugger.removeBreakpoint by breakpointId from set_breakpoint

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "breakpointId": "<breakpointId>"
    },
    "name": "remove_breakpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetIdNo
processIdNoProcess ID. If omitted, uses the single running app.
breakpointIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

C2.6/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false, which is consistent with removing a debugger breakpoint rather than data. The description adds nothing about idempotency, behavior on a missing or stale breakpointId, or whether removal affects a paused session — the questions an agent actually has for a removal operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with no filler, but it is under-specified rather than concise — the terseness comes at the cost of grammar and content, not from tight editing.

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?

A three-parameter mutation-adjacent tool with no output schema and only a single weak annotation needs the description to carry the load, and it does not: error behavior, ID provenance lifetime, and target/process scoping are all left implicit.

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

Parameters2/5

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

Schema coverage is only 33%: processId is documented in the schema, but targetId is undocumented everywhere. The description does add provenance for breakpointId ('from set_breakpoint'), which is genuine meaning beyond the schema, but it leaves the targetId/processId scoping relationship entirely unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment names a verb+resource ('removeBreakpoint by breakpointId') and links it to set_breakpoint, so an agent can infer it undoes a set_breakpoint call. However, 'Debugger.removeBreakpoint' is an internal API path rather than a plain statement of what the tool does, and the sentence is a noun phrase with no subject or object grammar.

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 phrase 'from set_breakpoint' implies the breakpoint must have been created by that sibling, which is a useful precondition, but there is no explicit when-to-use/when-not guidance, no statement about what to do if the ID is unknown, and no mention of any alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools