Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

pause

Halts JavaScript execution on a target Electron process through Chrome DevTools Protocol so you can inspect runtime state and debug issues.

Instructions

Pause JavaScript execution on a target via Debugger.pause

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

C2.8/5.0
Behavior2/5

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

The only annotation is destructiveHint=false, so the description carries most of the behavioral burden. It says what is paused and the underlying CDP command, but it does not explain that execution remains halted until resumed, what happens if no target is attached, or what side effects a caller should expect.

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 front-loaded sentence with no filler or redundant restatement. It is appropriately sized for a simple pause operation and gets to the action immediately.

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 debugging control tool with two parameters, only 50% schema description coverage, minimal annotations, and no output schema, the definition leaves out important operational context. Missing details include prerequisites, execution side effects, parameter selection, and how to resume execution.

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 50%: processId is documented in the schema, but targetId is not. The description says 'on a target' but adds no meaning about targetId, how to choose between targetId and processId, or what happens when both are omitted.

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 states a specific verb and resource: pause JavaScript execution, and identifies the mechanism via Debugger.pause. This is clear enough to distinguish it from generic command execution, but it does not explicitly contrast with relevant siblings such as cdp_command or evaluate.

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 definition gives no when-to-use or when-not-to-use guidance, and it does not name alternatives. It also omits the prerequisite that a target likely needs to be attached before pausing execution.

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