Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

ipc_invoke

Invoke a main-process IPC handle channel or emit an IPC event with arguments to debug Electron inter-process communication; requires inspectMain.

Instructions

Directly invoke a main-process IPC handle channel or emit an IPC event with arguments. Requires inspectMain.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "channel": "<channel>"
    },
    "name": "ipc_invoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNoArguments to pass to the IPC handle listener
channelYesIPC channel name (e.g. 'get-user-settings')
targetIdNo
processIdNoProcess ID. If omitted, uses the single running app.

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 declare openWorldHint=true and destructiveHint=false, and the description adds the inspectMain precondition, which is useful context beyond structured fields. However, invoking an arbitrary IPC handler can trigger real application side effects depending on the channel, and the description is silent on that risk, on failure modes for unknown channels, and on whether it waits for a response.

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?

Two short sentences, purpose front-loaded, prerequisite second. Nothing is wasted. It is arguably too terse for a tool with two distinct operating modes, but there is no padding or redundancy.

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 4-parameter tool with no output schema and open-world reach, the definition covers the prerequisite but omits what is returned, how errors surface for nonexistent channels, and how invoke mode differs behaviorally from emit mode. Adequate to attempt a call, not adequate to predict its outcome.

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 75%, with channel, args, and processId already documented in the schema; targetId is the only undocumented parameter. The description only echoes 'with arguments' and does not explain the invoke-versus-emit semantic, which is the key parameter-driven distinction. Baseline 3 is appropriate given the schema does most of the work.

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?

States a specific verb and resource: invoke a main-process IPC handle channel or emit an IPC event, with arguments. That distinguishes two modes of operation, which is genuinely informative. It stops short of naming the sibling tools it complements or supersedes (evaluate_main, ipc_tap, ipc_fuzz_and_verify), so the boundary is left implicit.

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

Usage Guidelines4/5

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

Gives an explicit prerequisite - 'Requires inspectMain' - which is exactly the kind of gating condition an agent needs before attempting a call. It does not say when to prefer this over evaluate_main or ipc_tap for the same goal, so the routing guidance is clear but not complete.

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