Skip to main content
Glama

hover

Move the mouse pointer over an element by reference or viewport coordinates to reveal hidden menus and tooltips in a browser tab, helping inspect UI that appears on pointer-over.

Instructions

Move the mouse over an element (by ref or coordinate) to reveal menus and tooltips.

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": {
      "tabId": "<tabId>"
    },
    "name": "hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoElement reference from read_page or find, e.g. "e12"
tabIdYesTab ID, from tabs_list or tab_create
coordinateNo[x, y] in viewport CSS pixels, as seen in a screenshot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does state the observable effect (revealing menus and tooltips), which signals a non-destructive interaction. It stops short of saying whether the hover state persists after the call, whether tooltips appear asynchronously, or how this differs from a click-triggered reveal.

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 front-loaded sentence with the action and its purpose, zero filler. Nothing is buried or restated.

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, single-action tool with full schema coverage and no output schema, the definition covers what to do and why. The only meaningful gap is lifecycle behavior of the hover state, which a slightly longer description could close.

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 ref, tabId, and coordinate are already fully documented with examples and units. The description only echoes the ref-or-coordinate choice, adding no new syntax or constraint meaning beyond the schema, so 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 and resource ("move the mouse over an element") plus the intent ("to reveal menus and tooltips"), which is clearly distinct from siblings like click or type. It doesn't explicitly name a sibling to contrast with, but the action is unambiguous.

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 phrase "to reveal menus and tooltips" implies the use case, so an agent knows to reach for this before clicking a submenu item. However, there is no explicit when-not guidance, no mention of using click instead when the goal is activation, and no note on pairing with screenshot to capture the revealed state.

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