Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

vision

Read-only

Captures a one-shot Electron app state with screenshot, page info, recent console errors, network failures, and open windows to diagnose issues quickly.

Instructions

One-shot app state: screenshot + page_info + recent console errors + network failures + windows

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

Input Schema

NameRequiredDescriptionDefault
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.
includeScreenshotNoInclude base64 PNG (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description isn't responsible for the safety profile. It does add real value by disclosing the five components returned, which is behavioral information beyond the annotations. However, with no output schema, it omits payload characteristics an agent would want — base64 PNG size, how many console errors count as 'recent', and whether missing windows/network data returns empty or errors.

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 terse line with the payload contents front-loaded and no filler. It reads as a fragment without a verb ('Returns...'), which costs a little clarity but 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?

Absent an output schema, the description should carry more of the return-shape burden; enumerating the five data sources is a good start but skips size/limit caveats and targeting semantics for a tool whose base64 screenshot payload can dominate a response. Adequate for a read-only aggregate, but incomplete on the details that affect how an agent issues the call.

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 67%, with processId and includeScreenshot documented but targetId bare. The description mentions no parameter at all — it does not clarify how processId/targetId select the target app, nor how includeScreenshot suppresses the screenshot component. The implicit linkage between 'screenshot' in the contents list and includeScreenshot is weak compensation, so this sits at the baseline rather than above it.

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 concrete composite operation — 'one-shot app state' — and enumerates exactly what it aggregates: screenshot, page_info, console errors, network failures, and windows. An agent can tell this is the batch/aggregate counterpart to the singular sibling tools like screenshot and page_info, though it never names those siblings explicitly.

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 word 'one-shot' implies this is the preferred first-look call for grabbing state in a single round-trip, but the description never states when to prefer this over calling screenshot and page_info separately, nor any preconditions. Usage must be inferred from the compact phrasing rather than read from it.

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