Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

hover

Move the pointer over a CSS selector or accessibility element to trigger mouseover menus without clicking.

Instructions

Move the pointer over a CSS selector (mouseover / hover menus). Does not click.

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": "hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoAccessibility element ref (e.g. 'e1', 'e12') from snapshot
selectorNoCSS selector to hover
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

A4/5.0
Behavior4/5

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

Annotations only supply destructiveHint=false, so the description earns credit for stating the non-clicking behavior and the hover-menu use case. It stops short of saying whether the call waits for transitions to settle or what state is left behind after the pointer moves.

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 front-loaded sentences with zero filler; the behavioral constraint is stated before any elaboration.

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 simple pointer-move action with no output schema and mostly documented parameters, this is nearly sufficient; only the outcome of the hover (menu opens, elements appear) is left unstated.

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 75%, so most parameters are documented in the schema itself. The description adds nothing about choosing between ref and selector, their precedence if both are given, or the undocumented targetId, so it does not compensate for the remaining gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb (move the pointer over) and target (CSS selector), plus the parenthetical mapping to mouseover/hover menus and an explicit negative scope ("Does not click") that separates it from the click sibling.

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?

Use is implied by "hover menus" and the "does not click" contrast, which hints that this is the right call for menu reveal flows, but there is no explicit when-to-use/when-not guidance or named alternative for element-targeted hovering.

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