Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

resume

Continue JavaScript execution on a paused Electron target through Chrome DevTools Protocol, selecting it by target or process ID.

Instructions

Resume JavaScript execution on a target via Debugger.resume

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": "resume"
  }
}

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.7/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 and adds little. It does not say what happens if the target is not paused (error? no-op?), whether execution continues until the next breakpoint, whether control returns immediately or blocks, or anything about the response.

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?

A single, front-loaded sentence with no filler or repetition. It is efficient, though the terseness contributes to the gaps noted in usage and parameter coverage rather than being purely a virtue.

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 debugger control operation with an undocumented parameter, minimal annotations (no readOnlyHint) and no output schema, the description is too thin. An agent cannot tell the precondition for success, the failure mode, or how to choose between targetId and processId.

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 50%: processId is documented in the schema (omit if only one app is running) but targetId has no description anywhere, and the description adds no meaning for either parameter. It does not explain how targetId and processId relate or which should be supplied when both a target and process exist.

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?

"Resume JavaScript execution on a target" states a specific verb and resource, and naming the underlying Debugger.resume method pins the effect to a known debugger operation. It is clearly distinct from siblings like evaluate or attach, though it never mentions its natural counterpart (a pause/breakpoint trigger) to anchor the pairing.

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?

There is no explicit when-to-use statement: it never says the target must currently be paused, nor what to do instead (e.g., step over/into, evaluate) when execution is already running. The only guidance an agent can extract is the implicit precondition baked into the word "resume".

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