Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

get_ipc_log

Read-only

Read and drain captured IPC messages after tapping a process, so you can inspect inter-process communication events during Electron debugging. Requires inspectMain.

Instructions

Drain / read captured IPC entries after ipc_tap. 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": "get_ipc_log"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is partly covered, and the description adds the inspectMain prerequisite and the ordering dependency on ipc_tap. However, it never clarifies whether "drain" actually empties the capture buffer (a potential side effect that sits in tension with readOnlyHint) nor what refreshFromMain changes behaviorally. With annotations present the bar is lower, but a 3 reflects these unresolved behavioral questions.

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, front-loaded with the action and followed by the prerequisite — nothing is padded. It is arguably too terse rather than bloated, but in terms of sizing and structure it is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Three parameters, no output schema, and a vague "Requires inspectMain" clause leave significant gaps: what a returned entry looks like, whether draining is destructive, and how tail/refreshFromMain interact. For a tool whose output shape is entirely undocumented, the description does not do enough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — only processId is documented in the schema. The description says nothing about tail (how many entries), refreshFromMain (what it re-fetches and from where), or override behavior for processId, so it does not compensate for the coverage gap.

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 concrete verb pair ("Drain / read") and a concrete resource ("captured IPC entries"), and ties itself to the sibling ipc_tap as the capture step. An agent can tell this is the retrieval counterpart to ipc_tap. It stops short of a 5 because "Drain" vs "read" leaves the consumption semantics ambiguous.

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?

"after ipc_tap" gives a clear sequencing condition, and "Requires inspectMain" surfaces a prerequisite the agent must satisfy before calling. There is no explicit when-not guidance or named alternative for reading non-IPC logs (e.g. get_network_log, get_logs), so it falls short of a 5.

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