Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

start_coverage

Starts precise JavaScript coverage tracking for an Electron process, optionally including CSS rule usage; pair with stop_coverage to measure executed code.

Instructions

Start JS precise coverage (optional CSS rule usage). Pair with stop_coverage.

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

Input Schema

NameRequiredDescriptionDefault
cssNoAlso track CSS rule usage
targetIdNo
processIdNoProcess ID. If omitted, uses the single running app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false, so the description carries most of the burden. The pairing sentence does disclose meaningful statefulness — coverage is a start/stop session rather than a one-shot query — which is real value beyond the annotation. However, it says nothing about whether starting twice resets prior data, whether an app must already be attached, or how results are retrieved.

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 compact sentences with the action front-loaded and no filler; the pairing hint is placed last where it reads as a follow-up note. The parenthetical "(optional CSS rule usage)" is slightly clipped, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter session-start tool with no output schema and only a destructiveHint annotation, the definition covers the core action and the pairing contract. It leaves the agent guessing about prerequisites (is an app required?) and about the lifecycle, which are the things most likely to cause a wrong invocation.

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?

Schema coverage is 67%, with targetId carrying no description at all. The description reinforces the css flag's meaning (optional CSS rule usage), but adds nothing about targetId or processId, leaving one parameter explained only by a terse schema string. That roughly matches the baseline for a mid-coverage schema.

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?

States a specific verb and resource ("Start JS precise coverage") plus an optional scope (CSS rule usage), which is enough to distinguish it from unrelated siblings. It also names its counterpart, stop_coverage, so the agent can tell it is the opening half of a session pair. It stops short of saying what 'precise' means versus any non-precise coverage mode.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Pair with stop_coverage" is the only usage cue, and it does usefully imply that this tool begins a session whose results come from the sibling. There is no explicit when-to-use rationale (e.g. use before interacting with the page, must be followed by stop to retrieve results) and no exclusions.

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