Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

stop_tracing

Idempotent

Stops CDP tracing and saves a JSON trace file for analysis in chrome://tracing.

Instructions

Stop CDP tracing and write a JSON trace file (open in chrome://tracing)

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_tracing"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoOutput file path (default: OS temp dir)
processIdNoProcess ID. If omitted, uses the single running app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and idempotentHint=true, so the mutation profile is already known; the description adds real value by disclosing the side effect (a JSON trace file is written) and its consumer (chrome://tracing). It stops short of stating whether the call fails when no trace is active, which is the main remaining behavioral unknown.

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?

A single front-loaded sentence with the action first and the resulting artifact second; there is no filler or redundancy, and the parenthetical viewer hint earns its place by telling the agent what to do with the output.

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

Completeness4/5

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

For a two-optional-parameter tool with annotations and no output schema, the definition covers action, side effect, and output format adequately. The only meaningful gap is the precondition that a tracing session must be active, which the agent must infer.

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 100% with both optional parameters (path, processId) fully documented in the schema, so the baseline is 3. The description adds nothing about parameter behavior beyond the schema, and its '(open in chrome://tracing)' note describes the output format rather than how to use path or processId.

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 gives a specific verb plus resource ('Stop CDP tracing') and names the concrete artifact produced ('write a JSON trace file'), so an agent knows exactly what happens. It does not name start_tracing as its counterpart, but the start/stop pairing is self-evident from the verb.

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?

Usage is only implied: an agent can infer this is called after start_tracing to finalize a capture. There is no explicit when-to-use statement, no mention of what happens if tracing was never started, and no guidance about which sibling (e.g. stop_cpu_profile, stop_coverage) to prefer for other capture types.

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