Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

webcontents_topology

Read-only

Maps BrowserWindows and webContents to CDP targets to enable debugging of Electron apps. Requires inspectMain.

Instructions

Map BrowserWindows / webContents (main) to CDP targets. 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": "webcontents_topology"
  }
}

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?

The readOnlyHint annotation already establishes that this is a safe read, so the bar is lower. The description still contributes by disclosing the inspectMain prerequisite, which is real operational context an agent would otherwise only discover at failure time. It does not say what the mapping looks like, whether it is cached or live, or what happens when multiple apps are running.

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 short sentences with zero filler, and the core operation is front-loaded before the prerequisite. Nothing here could be cut without losing information.

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 one-optional-parameter read tool with full schema coverage and a readOnly annotation, the definition covers what it does and the key prerequisite. The gap is that it never characterizes the result of the mapping, which matters for a topology/discovery tool whose output feeds subsequent target selection, and there is no output schema to compensate.

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 the single processId parameter and its fallback behavior ("If omitted, uses the single running app") are already fully documented in the schema. The description adds nothing about processId, which is acceptable given the schema carries that burden, but it earns no extra credit.

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 states a concrete verb and resource: "Map BrowserWindows / webContents (main) to CDP targets." That is specific enough to separate it from siblings like cdp_command or evaluate_main, which act on a target rather than enumerate the mapping. The only weakness is the jargon-heavy phrasing, but the operation itself is unambiguous.

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?

Usage is implied rather than stated: an agent can infer this is a discovery step that precedes target-specific calls, and "Requires inspectMain" signals a prerequisite. However, there is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g. attach_by_pid) for the case where a process ID is already known.

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