Skip to main content
Glama

ie_hover

Hover over a page element to open menus or tooltips, including in legacy IE mode windows, frames, and attached tabs.

Instructions

Hover the mouse over an element (for menus/tooltips). Over COM (target hwnd:/tab:) mouseover and mouseenter events are fired by script: synthetic, the mouse does not move.

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": {
      "by": "<by>",
      "value": "<value>"
    },
    "name": "ie_hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
byYes
waitNo
frameNo
valueYes
targetNoWhere to act: omit it for the session's IE driver; hwnd:<n> acts over COM on the window <n> (a modal dialog's hwnd from a NOTICE or ie_windows), tab:<n> on an attached tab. Over COM, DOM access is script, input is synthetic (script events and a timer click, not mouse or keyboard input; keys are posted window messages) and only id, name, tag, class, link_text and (documentMode 8+) css locators work.
timeoutNoseconds to wait for the element (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and it does disclose a genuinely non-obvious trait: over COM the mouseover/mouseenter events are fired by script and the pointer never moves. It stops short of covering the session-driver path (whether a real pointer move occurs, whether the element must be scrolled into view, or what side effects hover can trigger).

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?

Two tight sentences with the core action front-loaded and the COM caveat immediately after. No filler, though the second sentence is a dense run-on that mixes event semantics with locator restrictions.

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 6-parameter mutation-like interaction tool with no annotations and no output schema, the description covers the COM behavioral surprise well but leaves the locator parameters (by/value) and wait/frame unexplained, which an agent needs to call it correctly.

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 coverage is only 33%; only 'target' and 'timeout' are documented in the schema, and the description restates only the target routing (hwnd:/tab:). The four remaining parameters (by, value, wait, frame) get no meaning from either the schema or the description, so the description fails to compensate for the coverage gap.

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 gives a specific verb and resource ('Hover the mouse over an element') and adds a use-case gloss ('for menus/tooltips') that tells an agent what the action is for. It is clearly distinct from siblings like ie_click or ie_fill, though it never names an alternative explicitly.

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?

The parenthetical '(for menus/tooltips)' implies the intended scenario, which is useful, but there is no explicit when-not guidance or pointer to an alternative (e.g., using ie_js to trigger a handler). Usage is implied rather than stated.

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