Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

get_dom

Read-only

Retrieve full page HTML or a specific element's outerHTML from an Electron app by CSS selector, enabling DOM inspection during debugging.

Instructions

Read documentElement.outerHTML or a specific element's outerHTML

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_dom"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorNoOptional CSS selector; omit for full documentElement.outerHTML
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.4/5.0
Behavior3/5

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

The read-only nature matches the readOnlyHint annotation, so the description adds nothing contradictory there. It omits behavior an agent would want: omitting the selector returns the full document, which can be very large, and there is no note on output size or truncation.

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?

One tight sentence that front-loads the main outcome. It is efficient, though extremely terse, with no wasted wording.

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 read-only tool with no output schema, the definition is minimally adequate, but it leaves gaps around the undocumented targetId parameter and the practical implications of requesting a full-document read (size, potential performance cost).

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 67% and the schema already documents selector and processId. The description restates the selector behavior but says nothing about targetId, which is undocumented in both places, so it only marginally compensates.

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?

Specific verb (read) plus resource (documentElement.outerHTML / element outerHTML), and it distinguishes document-level from element-level reads. It doesn't differentiate itself from nearby readers like capture_mhtml or get_response_body, so it falls short of 5.

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?

Implies the selector/no-selector usage pattern, but gives no explicit when-to-use guidance against alternatives that also return page content (capture_mhtml, get_response_body). Usage is inferable rather than stated.

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