Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

highlight

Scrolls a CSS selector into view and paints a CDP overlay to visually locate UI elements; set durationMs to auto-hide the marker.

Instructions

Scroll a CSS selector into view and paint a CDP overlay highlight (auto-hides when durationMs > 0)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "selector": "<selector>"
    },
    "name": "highlight"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYes
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.
durationMsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations only supply destructiveHint=false, so the description does the real work here: it discloses that a CDP overlay is painted and that it auto-hides when durationMs > 0. It omits what happens when durationMs is 0 or omitted (does the highlight persist?), and whether the call waits for the scroll to settle or returns the element's position.

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?

A single tight sentence with the primary action front-loaded and the conditional effect trailing in parentheses. Nothing is padded, though the parenthetical reads slightly compressed.

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?

With four parameters, 25% schema coverage, no output schema, and only a single annotation, the description is too thin: it never says what the call returns, whether the highlight persists after durationMs=0 or omission, or how `targetId` selects a target. These are exactly the gaps the description should close when structured fields don't.

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 25% — just `processId` is documented. The description hints that durationMs controls auto-hide timing, but `selector` and especially `targetId` get no added meaning, and the relationship between `targetId` and `processId` is left unexplained.

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 uses a specific verb phrase ("Scroll a CSS selector into view") plus an added effect ("paint a CDP overlay highlight"), which tells an agent both the scrolling and the visual-debugging behavior. It is distinguishable from the plain `scroll` sibling because of the overlay painting, though it never names or contrasts that 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose this over `scroll`, `act_and_verify`, or `assert_ui`, and no stated prerequisites for the overlay to work (e.g., an attached target). The only conditional is the parenthetical about auto-hide, which describes behavior rather than when-to-use.

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