Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

hover

Move the real mouse pointer over an element matched by a CSS selector to trigger pointer-over UI such as tooltips and menus.

Instructions

Hover over an element using real mouse movement

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
tabIdNoTab ID (optional)
selectorYesCSS selector of the element

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.2/5.0
Behavior3/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 one meaningful trait: the hover uses real mouse movement rather than a synthetic JS event, which matters for CSS :hover state and event handlers. It omits other relevant behavior such as whether the element is scrolled into view first, what happens if the selector matches nothing, or whether the cursor position persists afterward.

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?

A single front-loaded sentence with zero filler, which is efficient for a simple two-parameter action. The terseness edges toward under-specification, but nothing in the sentence is wasted.

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 simple, fully schema-documented tool with no output schema, the description is minimally sufficient to call it correctly. It falls short on failure behavior and element-visibility handling, which an agent would need when a hover silently does nothing.

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%, with both tabId and selector documented in the schema itself, so the baseline is 3. The description adds no extra meaning about selector resolution, matching multiple elements, or tabId defaults.

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 names a specific verb and resource ("Hover over an element") plus a mechanism ("real mouse movement"), so an agent knows exactly what action is performed. It does not explicitly differentiate itself from siblings like click or drag, but the verb is unambiguous enough to be selected on its own terms.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose this over click, drag, or execute_javascript, and no mention of the typical motivating scenario (revealing hover-only menus or tooltips). The agent must infer usage entirely from the verb.

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