Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

doctor

Read-onlyIdempotent

Checks local Electron debugging prerequisites—package/Node/platform, Electron binary, env flags, managed process count, and optional localhost free-port sample—to verify environment health.

Instructions

Local environment health check: package/node/platform, Electron binary, env flags, managed process count, optional free-port sample (localhost bind only)

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

Input Schema

NameRequiredDescriptionDefault
sampleFreePortNoIf true (default), allocate a free 127.0.0.1 port sample via bind; no remote network

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is established structurally. The description adds useful extra context — it is a local-only check and the port sampling binds to localhost with no remote network — but says nothing about cost, timing, or what a failed check looks like. Given the lower bar set by annotations, this is adequate but not rich.

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 sentence with the purpose front-loaded and the inspected items compactly enumerated after a colon. No filler, no repetition, and the optional parameter caveat is placed at the end where it belongs.

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, zero-required-parameter health check with annotations covering safety and no output schema to explain, the description is close to self-sufficient: it names what is examined and the network scoping. The only real gap is that it does not hint at the shape of the report (pass/fail items, severity), which would help an agent interpret results.

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% on the single optional parameter, and the schema already explains that true (the default) allocates a 127.0.0.1 port with no remote network. The description's parenthetical 'optional free-port sample (localhost bind only)' largely restates that. Baseline 3 applies since the schema 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?

The description opens with a specific verb+resource framing ('Local environment health check') and then enumerates exactly what is inspected: package/node/platform, Electron binary, env flags, managed process count, and port sample. That is far more concrete than a bare 'doctor' name, and the 'local' scope distinguishes it from remote/network diagnostics. It does not, however, explicitly contrast itself with the similarly purposed 'diagnose' sibling.

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 implied rather than stated: an agent can infer this is the pre-flight/sanity tool for verifying a local Electron+Node setup. There is no explicit when-to-use, when-not-to-use, or named alternative, and the presence of a 'diagnose' sibling means the boundary is left to inference.

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