easy-ui-mcp

Overview Schema Source Related Servers Discussions Admin

ui_hover

ui_hover

Hover over a matched element to reveal hover- or mouseenter-triggered content like dropdown menus. Use the selector from ui_get_page_state to target the correct element.

Instructions

Move the pointer over the single element matching the selector, to reveal :hover or mouseenter content such as dropdown menus. Use the selector from ui_get_page_state. Selectors containing "nth=" are positional: call ui_get_page_state again after the page changes before reusing them.

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

Input Schema

Name	Required	Description	Default
`selector`	Yes	CSS selector, or the `selector` value of an element from ui_get_page_state, passed unchanged
`session_id`	No	Which open session to act on, as returned by ui_start_session. Optional with one open session; required when several are open.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses useful behavior — a single matching element, the hover/mouseenter effect, and selector staleness — but says nothing about what happens when no element matches or several match, whether the element is scrolled into view, or any waiting behavior.

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?

Three short sentences, front-loaded with what the tool does, then where the selector comes from, then the caveat. Every sentence carries actionable information with no filler.

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 two-parameter interaction tool with no output schema, the definition covers purpose, selector sourcing, and the main failure trap. The main remaining gap is error/no-match semantics, which matters somewhat with no annotations to fall back on.

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 100%, so both parameters are already documented, establishing a baseline of 3. The description adds a little meaning, notably that the selector must be passed unchanged and that nth= selectors are positional, but it doesn't explain the session_id parameter at all.

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?

The description gives a specific verb and resource (move the pointer over the element matching the selector) and states the observable purpose — revealing :hover or mouseenter content such as dropdown menus. This distinguishes it from click-type siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It explicitly routes the agent to take the `selector` from ui_get_page_state and warns that positional (nth=) selectors must be re-derived after a page change. It doesn't contrast hover with alternatives like ui_click for opening menus, but the when-to-use context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.