Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

start_tracing

Start Chrome DevTools Protocol performance tracing for an Electron app, optionally selecting a target, process, and trace categories. Use with stop tracing to capture and analyze performance data.

Instructions

Start Chrome DevTools Protocol performance tracing (pair with stop_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": "start_tracing"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetIdNo
processIdNoProcess ID. If omitted, uses the single running app.
categoriesNoComma-separated CDP trace categories (default: timeline + v8)

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 supply destructiveHint=false, so the description carries most of the burden. It usefully implies a start/stop lifecycle (a trace buffer is opened and must be closed), but it doesn't say whether an in-progress trace is overwritten, whether the call blocks, or where the captured trace is retrievable.

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?

One sentence plus a short parenthetical, front-loaded with the action and resource. Nothing is wasted and the pairing hint is placed where it is immediately useful.

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?

There is no output schema and no annotation coverage beyond non-destructiveness, yet the description never explains how the collected trace is obtained after stop_tracing or what the categories parameter materially changes. For a three-parameter capture tool, that leaves an agent unable to complete the workflow from this definition alone.

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%: processId's default-to-single-app behavior and the categories default are already documented in the schema, so the description adds nothing there. The remaining targetId parameter is undocumented in both schema and description, leaving a gap the description should have closed.

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 names a specific verb and resource ('Start Chrome DevTools Protocol performance tracing'), which is enough to separate it from siblings like start_coverage or start_cpu_profile, though it doesn't explicitly say why to choose tracing over those. The parenthetical 'pair with stop_tracing' reinforces scope.

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_tracing' gives lifecycle guidance that a start tool genuinely needs. However, it never states when this tool is preferable to start_coverage or start_cpu_profile, nor what happens if tracing is already running.

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