Skip to main content
Glama

browser_hover

Read-onlyIdempotent

Hover the mouse over an element (reveals tooltips + hover menus). ref is an aria-ref token from browser.snapshot or a CSS selector; frame (optional) is the CSS selector of an a CSS ref lives in.

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

Input Schema

NameRequiredDescriptionDefault
refYes
frameNo
page_idYes
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / frame
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Frame"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description is not the only source of safety information. It still adds genuine behavioral context by noting that hovering mutates visible UI state (tooltips and hover menus appear) — a side effect an agent needs to anticipate even though nothing is clicked or destroyed.

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 sentences, front-loaded with the action and its effect before parameter details. There is essentially no filler; a slightly cleaner split between action and parameter notes would be the only improvement.

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?

This is a simple interaction tool with no output schema and full annotation coverage, so the description's remaining obligations are small. It handles the two interesting parameters and the hover effect; only `page_id` and what the call returns/whether state persists are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25%, with no schema-level descriptions for `ref` or `frame`, yet the description explains that `ref` accepts either an aria-ref token from browser.snapshot or a CSS selector, and that `frame` is the CSS selector of an iframe containing a CSS-based ref — a real disambiguation the schema lacks. `page_id` remains undocumented in both places, keeping it short of a 5.

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 states a specific verb and resource ('Hover the mouse over an element') and adds the observable effect ('reveals tooltips + hover menus'), which makes the intent concrete. It does not explicitly contrast itself with neighboring actions like browser_click or browser_mouse, so sibling differentiation is left implicit.

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 about tooltips and hover menus implies when the tool is appropriate (triggering hover-only UI), but there is no explicit when-to-use/when-not-to-use guidance and no named alternative such as browser_click for actual activation. Usage is inferable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.