Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

stop_coverage

Idempotent

Stops JavaScript and optional CSS coverage collection and returns the results, with an option to write them to JSON for analysis.

Instructions

Stop coverage and return JS (and optional CSS) coverage data; optionally write JSON

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

Input Schema

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

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 already declare readOnlyHint=false and idempotentHint=true, so the mutation profile is covered. The description adds useful detail about the returned coverage payload and the optional JSON write, but omits where the JSON is written, whether stopping is destructive to collected data, and the no-active-session behavior.

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?

One compact, front-loaded clause with no wasted wording; the verb leads and the returns/write behavior follows. The semicolon packing is terse to the point of ambiguity about the output path, but nothing is redundant.

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?

With no output schema and an undocumented parameter, the description should carry the burden of describing the coverage payload shape and the JSON destination, which it does not. An agent can see what the tool does but not what it will get back or where files land.

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, but 'path' has no description. The phrase 'optionally write JSON' hints at an output path but never says whether 'path' is the output file or a project path, leaving the undocumented parameter ambiguous.

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?

Specific verb+resource: 'Stop coverage' plus what it returns ('JS (and optional CSS) coverage data') and the optional JSON write. It implicitly pairs with start_coverage but never names or contrasts that sibling, so differentiation rests on the name alone.

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?

No when-to-use guidance: it doesn't state that a coverage session must already be running (start_coverage), what happens if none is active, or when to prefer the JSON-write mode over the returned data.

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