Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

heap_snapshot

Idempotent

Captures a V8 heap snapshot for an Electron process to investigate memory leaks. Saves the .heapsnapshot file to a specified path for later analysis.

Instructions

Take a V8 heap snapshot (.heapsnapshot) for leak investigation

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and idempotentHint=true, and the description is consistent with that by describing artifact generation. Beyond the annotations it adds the output file type, which is useful, but it omits important behavior: that the snapshot is written to 'path', that it can be large and pause or burden the inspected process, and any expected latency.

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 tight sentence with the action and purpose front-loaded and no filler. Nothing is wasted, though the compactness is partly what leaves the parameter gaps unaddressed.

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?

For a three-parameter tool with no required parameters, no output schema, and low schema coverage, the description is too thin: it never explains the destination file semantics, how target selection defaults work, or the cost of the operation. An agent could invoke it but could not predict where the artifact goes or which process gets snapshotted.

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 description coverage is only 33% - only processId is documented in the schema - yet the description says nothing about 'path' (where the file lands) or 'targetId' (which target to snapshot). With two of three parameters undocumented in both places, the description fails to compensate for the coverage gap.

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 (take a V8 heap snapshot), states the output artifact (.heapsnapshot), and gives the use case (leak investigation). It does not explicitly distinguish itself from the similarly named 'snapshot' or 'perf_snapshot' siblings, so the differentiation is only partial.

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 phrase 'for leak investigation' implies the scenario in which this tool is appropriate, but there is no explicit when-not guidance and no named alternative (e.g., perf_snapshot for CPU profiling or snapshot for DOM capture). The agent must infer the boundary.

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