Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

diagnose

Read-only

Summarize Electron process health by checking debug port reachability, target roles, recent console errors, and discovered local debug ports for one or all managed processes.

Instructions

Summarize process health: debug port reachability, target roles (page/worker/browser), recent console errors, and discovered local debug ports

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

Input Schema

NameRequiredDescriptionDefault
processIdNoOptional process id; omit to diagnose all managed processes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds real value beyond that by stating exactly which checks are performed (port reachability, role detection, console error collection, port discovery). It stops short of saying how results are structured or how expensive the scan is across many processes, which matters with no output schema.

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 verb leads and the list of health dimensions follows. The parenthetical role enumeration is slightly dense but every clause names a distinct check performed.

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 read-only, one-optional-parameter tool with no output schema, the description covers what an agent needs: the scope (one process or all) and the kinds of findings returned. Only the relationship to the overlapping "doctor" tool is left unaddressed.

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 100% and the description adds no additional meaning about processId beyond the schema's own note that omitting it diagnoses all managed processes. Baseline 3 is appropriate since the schema already carries the parameter semantics.

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?

"Summarize process health" is a specific verb+resource, and the description enumerates the concrete contents of that summary (debug port reachability, target roles, console errors, discovered debug ports). It does not, however, differentiate itself from the similarly-scoped sibling "doctor", so an agent must still guess between them.

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 by the word "diagnose" and by the parameter note about omitting processId to cover all managed processes. There is no explicit when-to-use, when-not-to-use, or named alternative such as "doctor" for the agent to route on.

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