Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

ipc_schema_inference

Read-only

Infer IPC channel contracts and argument shapes from captured traffic, then generate TypeScript interfaces for Electron app debugging.

Instructions

Infer IPC channel contracts, argument shapes, and generate TypeScript interfaces from captured IPC tap traffic. 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_schema_inference"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoOptional specific channel to analyze
processIdNoProcess ID. If omitted, uses the single running app.
refreshFromMainNoWhether to drain new IPC entries from main before analyzing (default: true)

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?

readOnlyHint=true already tells the agent this is non-mutating, and the description usefully confirms the tool consumes tap traffic rather than producing it. It does not disclose that refreshFromMain drains the main-process buffer (a consumptive side effect) or how much captured traffic is needed for reliable inference, both of which matter for a read-only-labelled tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the capability and the output artifacts, followed by the hard prerequisite. Nothing is redundant or wasted.

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

Completeness4/5

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

For a three-optional-parameter tool with no output schema, the description covers what it produces, where the data comes from, and the key dependency. Only the confidence/sample-size question about inference quality is left unaddressed.

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 description coverage is 100%, so channel, processId, and refreshFromMain are already fully documented, establishing a baseline of 3. The description adds no parameter-level detail beyond implying the channel scope in its first clause.

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 specific verb+resource pair ('Infer IPC channel contracts') and enumerates the outputs (argument shapes, TypeScript interfaces) plus the data source (captured IPC tap traffic). It is clearly distinct from a raw log tool like get_ipc_log, though it does not name any sibling 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?

'Requires inspectMain' gives one hard precondition, which is genuinely useful routing information. However, it never states when to choose this over get_ipc_log or ipc_tap, nor what happens if no tap traffic has been captured yet — usage 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