Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

set_breakpoint

Sets a breakpoint by URL and zero-based line number in Electron apps so you can pause execution and inspect runtime state.

Instructions

Debugger.setBreakpointByUrl (0-based lineNumber). Keep debugger enabled while BPs exist.

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": {
      "lineNumber": "<lineNumber>"
    },
    "name": "set_breakpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
targetIdNo
urlRegexNo
processIdNoProcess ID. If omitted, uses the single running app.
lineNumberYes
columnNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations only supply destructiveHint=false, so the description carries most of the burden; it does add a genuinely useful behavioral constraint (the debugger must remain enabled while breakpoints exist). However, it says nothing about persistence across navigations, when the breakpoint actually resolves, or that a returned breakpoint id is typically needed to remove it.

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?

Two short sentences with the most important detail (0-based line numbers) front-loaded and no filler. It is efficient, though the CDP-method phrasing is slightly opaque to an agent unfamiliar with the protocol.

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 six-parameter debugger operation with near-zero schema documentation and no output schema, the description is too thin: it does not explain how url/urlRegex select the script, nor what the caller receives back that would let them later remove the breakpoint.

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 description coverage is only 17%, so the description must compensate, and it adds meaning for just one parameter by declaring lineNumber 0-based. The relationship between url and urlRegex, what targetId scopes, and why url/urlRegex are optional while lineNumber is required are all left undocumented.

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 names a specific verb and resource ('setBreakpointByUrl') and specifies that line numbers are 0-based, so an agent can identify the operation. It leans on the CDP method name rather than plain language, and does not explicitly contrast with remove_breakpoint, but the purpose is unambiguous.

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?

'Keep debugger enabled while BPs exist' is a precondition about lifecycle, not guidance on when to choose this tool over alternatives. Nothing says when to use url versus urlRegex, or how this relates to breakpoint removal or other debugger tools.

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