Skip to main content
Glama

Hover

browser_hover

Move the mouse over an element identified by its ref to trigger hover menus and reveal hover-dependent UI.

Instructions

Move the mouse over an element identified by ref (useful for hover menus).

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": {
      "ref": "<ref>"
    },
    "name": "browser_hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesElement ref

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description must carry the full behavioral burden, and it does establish the key non-destructive fact that the mouse merely moves rather than activating the element. It is silent on failure behavior for a stale or invalid ref, whether the element is scrolled into view first, and whether hover-triggered listeners fire before the call returns.

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?

One sentence, front-loaded with the action and target, with the use case in a tight parenthetical. Nothing is redundant, though the parenthetical could have been turned into a stronger conditional clause.

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 single-parameter, non-destructive pointer tool with no output schema, the definition covers the essentials: what moves, over what, and why. The remaining gap is procedural context, namely where refs come from and what a failed hover returns.

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% for the single 'ref' parameter, so the schema already documents it fully and the baseline applies. The description's phrase 'identified by ref' restates the schema rather than adding format or sourcing details, such as where a ref is obtained (presumably browser_snapshot).

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 definition pairs the specific verb 'Move the mouse over' with the target resource 'an element identified by ref', which clearly separates it from mutation siblings such as browser_click or browser_type. It stops short of a 5 because it never names a sibling to contrast against, leaving the distinction to be inferred from the verb alone.

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 '(useful for hover menus)' supplies one concrete scenario, which is more than nothing. However, there is no guidance on when not to use it, no mention of whether it is a required precursor to clicking a revealed menu item, and no named alternative.

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