Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

get_process_health

Read-only

Diagnose Electron renderer crashes, window hangs, responsiveness issues, and process memory problems to identify unhealthy app processes.

Instructions

Watchdog health check diagnosing renderer crashes (OOM, killed), window hangs, responsiveness, and process memory

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

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

B3.2/5.0
Behavior3/5

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

With readOnlyHint=true already declaring this a safe read, the description adds value by naming the diagnostic checks it performs (OOM kills, hangs, responsiveness, memory). It says nothing about whether the check is passive snapshot vs. actively probing the app, how long it takes, or whether it can perturb a hung process — relevant for a watchdog on a hung target.

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 no filler; the diagnostic scope is stated immediately. It is a noun-phrase fragment rather than a full sentence, but this costs little and wastes nothing.

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?

There is no output schema, so the description ideally should indicate what the health result looks like (a verdict, a list of detected issues, memory figures). It also leaves targetId unexplained. For a zero-required-parameter diagnostic tool it is adequate but has clear gaps.

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 coverage is only 50%: processId has a description ('If omitted, uses the single running app'), but targetId is completely undocumented. The description mentions no parameters at all, so it fails to compensate for the undocumented targetId or clarify how targetId and processId interact.

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 uses a specific verb+resource combination ('Watchdog health check') and enumerates the concrete failure modes it diagnoses (renderer crashes OOM/killed, window hangs, responsiveness, process memory). It doesn't differentiate itself from nearby sibling diagnostics tools like 'diagnose', 'doctor', or 'get_performance_metrics', so it stops short of a 5.

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 it should be called when suspecting crashes, hangs, or memory pressure. There is no explicit statement of when to prefer this over 'diagnose', 'doctor', or 'get_performance_metrics', and no prerequisites or exclusions are given.

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