Skip to main content
Glama

hover

Moves the mouse over an element to reveal tooltips, menus, and CSS mouseover styles; the element is scrolled into view first.

Instructions

Moves the mouse over an element (scrolled into view; fails when hidden or covered) so hover menus, tooltips and :hover styles appear.

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

Input Schema

NameRequiredDescriptionDefault
tab_idNoDefault: the active tab.
selectorYesCSS selector, 'host >>> inner' (into an open shadow root or same-origin iframe) or snapshot ref (e12).
instance_idNoDefault: 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-rc.1

TDQS

A4/5.0
Behavior4/5

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

Annotations only carry destructiveHint=false, so the description does real work: it discloses the implicit scroll-into-view side effect and the two concrete failure modes (element hidden, element covered by another element). It does not say how failure surfaces (exception vs result) or whether the hover persists after the call returns, which keeps it off a 5.

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?

A single sentence with the action first, the automatic scrolling and failure conditions parenthesised, and the payoff last. Every clause carries information an agent needs and nothing is padded.

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 three-parameter, fully documented, non-destructive browser action with no output schema, the description covers what it does, what it scrolls and what makes it fail. The only shortfall is the absence of any hint about what a successful call gives back, which matters because the point of hovering is usually to then inspect revealed content.

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 description coverage is 100%, so all three parameters (tab_id, selector, instance_id) are already documented in the schema, including the shadow-root/iframe and snapshot-ref selector forms. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 ('moves the mouse') and a specific target ('over an element'), then states the visible outcome: hover menus, tooltips and :hover styles appear. That is enough to tell it apart from click_element or scroll, but it never names a sibling or states the boundary explicitly, so it stops short of a 5.

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?

Usage context is clear and actionable: reach for this tool when you need hover-only UI (menus, tooltips, :hover styles) to become visible, and it implicitly rules out hidden or covered targets since it fails there. What is missing is guidance on sequencing with siblings, e.g. whether to snapshot before or after hovering to capture the revealed menu.

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