Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

start_cpu_profile

Start V8 CPU profiling on an Electron page target to capture performance data, then pair with stop_cpu_profile to end the session.

Instructions

Start V8 CPU profiler on a page target (pair with stop_cpu_profile)

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations supply only destructiveHint=false, so the description carries most of the behavioral burden and adds the lifecycle hint that a companion stop call is needed. It does not say where profiling data is stored, how long collection runs, whether a prior profile is discarded, or how results are retrieved. For a stateful profiler starter with no output schema, that is a meaningful gap.

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 a clear verb, resource, scope, and pairing note — nothing wasted. It is arguably over-terse, since a few more words on lifecycle and data retrieval would have cost little.

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 small two-parameter starter tool, the definition covers what it does and its companion call, and no output schema exists to explain. It still leaves the agent uninformed about where the collected profile ends up, how to retrieve it, and whether the profiler must be stopped before results are available — gaps that matter for a stateful operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: processId is documented as "omitted, uses the single running app", while targetId has no schema description at all. The description's "on a page target" supplies the missing meaning for targetId, tying it to a browser page target rather than an arbitrary identifier, which is the compensation this coverage level requires.

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 V8 CPU profiler") and scopes it to "a page target", which is more precise than the bare name. It also names the sibling stop_cpu_profile as its pair, so an agent can place it in the profiler lifecycle without consulting other definitions.

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?

The parenthetical "pair with stop_cpu_profile" implies the intended workflow, but there is no explicit statement of when to reach for CPU profiling versus start_tracing or start_coverage, nor any prerequisites or exclusions. Usage is implied rather than spelled out.

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