Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

main_state

Read-only

Inspect Electron main-process state to retrieve windows, app paths, versions, and metrics; requires an inspectMain or node target.

Instructions

Electron main-process nervous system: windows, app paths, versions, metrics (requires inspectMain / node target)

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

C2.9/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read, so the description's added value is the prerequisite disclosure: the tool only yields data when the main process is launched with inspectMain / a node target. That is real behavioral context beyond the annotations. It stops short of saying what happens when the precondition is unmet (error vs empty result) or whether the result is a one-time snapshot.

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?

One compact sentence with the content list front-loaded and the prerequisite trailing as a qualifier. The "nervous system" metaphor consumes a few words without adding precision, but there is no redundancy or filler beyond that.

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?

For a single-optional-parameter read tool with no output schema, the description helpfully enumerates the returned data categories and notes the launch prerequisite, which covers most of what an agent needs. It leaves unclear the failure mode when inspectMain is absent and whether multiple processes can be enumerated, which matters for a state-inspection tool.

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?

With a single parameter at 100% schema description coverage, the schema already explains processId and its default ("uses the single running app"). The description adds nothing about processId behavior, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource domain concretely by enumerating what it surfaces (windows, app paths, versions, metrics), but the framing is metaphorical ("nervous system") rather than a verb+resource statement like "read main-process state." An agent can guess this is a read of main-process internals, but the exact operation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical "requires inspectMain / node target" gives a precondition for the tool working, which is useful, but there is no guidance on when to choose this over siblings such as evaluate_main for reading main-process data. The agent must infer the split between this and other main-process tools.

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