Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

ipc_tap

Installs a main-process IPC tap to capture and inspect ipcMain.handle calls and webContents send/ipc-message traffic; requires main-process inspection.

Instructions

Install main-process IPC tap (ipcMain.handle wrap + webContents send/ipc-message). Requires inspectMain.

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

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

A3.6/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false, and the description adds that this monkey-patches live IPC handlers inside the main process — useful context the annotations lack. However it says nothing about whether the tap can be removed, whether it alters app behavior or performance, or whether a restart is needed, which matters for a runtime mutator.

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 compact sentences, front-loaded with the action and followed by the prerequisite — no filler. The parenthetical is dense jargon but earns its place by naming exactly what gets wrapped.

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?

With no output schema and a single optional parameter the surface is small, and the prerequisite is covered. Still missing whether the tap persists across reloads, how to disable it, and what confirms successful installation — meaningful gaps for an instrumentation 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?

Only one parameter (processId) and schema description coverage is 100%, so the schema already explains the PID-or-default behavior. The description adds no further meaning about processId or what happens in multi-app scenarios; baseline 3 applies.

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: 'Install main-process IPC tap', then names the mechanisms it patches (ipcMain.handle wrap, webContents send/ipc-message). This is clearly an instrumentation-installer, distinguishable from the read-only sibling get_ipc_log, though it never explicitly contrasts with it.

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?

The clause 'Requires inspectMain' gives a concrete prerequisite, which is the main usage gate for this tool. It stops short of saying when to choose this over ipc_fuzz_and_verify or that get_ipc_log must be called afterwards to see results, so the workflow ordering is only implied.

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