Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

stop_cpu_profile

Idempotent

Stops CPU profiling and saves the collected data to a .cpuprofile JSON file, with optional custom output path and target Electron process selection.

Instructions

Stop CPU profiler and write a .cpuprofile JSON file

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and idempotentHint=true, so the mutating-but-repeatable profile is already structured. The description adds the useful fact that the call writes a .cpuprofile file to disk, which explains the non-read-only side effect, but it omits failure behavior when no profiling session exists and does not describe the returned result.

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 that identifies the action and its output artifact with no filler. It is efficient, though nearly too short to convey prerequisites or failure modes.

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 zero-required-parameter stop tool with full schema coverage and annotations stating it is non-read-only but idempotent, this is largely sufficient. The only meaningful gap is the absence of any note about erroring when no profiler is active or no app is running.

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 description coverage is 100%, with both 'path' (default OS temp) and 'processId' (defaults to the single running app) documented in the schema itself. The description adds no extra meaning about these parameters, so the baseline 3 applies.

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 ('Stop') and resource ('CPU profiler') plus the concrete artifact produced ('write a .cpuprofile JSON file'), so the operation and its effect are unambiguous. It does not explicitly name its counterpart start_cpu_profile, so sibling differentiation is only implied by the name.

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?

There is no explicit when-to-use statement, no prerequisite that a profiler must already be running, and no note about what happens if none is active. Usage is only implied through the obvious naming pair with start_cpu_profile.

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