Skip to main content
Glama
Sign In
Browser MCP

Browser MCP

by drisplabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Hover Element

hover

Simulate mouse hover over a specified element to trigger hover menus and tooltips without clicking.

Instructions

Move mouse over an element without clicking. Triggers hover 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": {
      "eid": "<eid>"
    },
    "name": "hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
eidYesElement ID from find results or the page snapshot.
page_idNoPage ID. If omitted, operates on the most recently used page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / page_id / description
      Added value: +"Page ID. If omitted, operates on the most recently used page."
  2. First observedv4.6.4

TDQS

A3.7/5.0
Behavior3/5

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

Adds behavioral context that it triggers hover menus and tooltips, which is useful. However, with no annotations, more detail would be helpful, e.g., whether it returns anything or if it waits for effects.

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?

Two short sentences that directly convey the purpose and a key behavioral effect. No extraneous words; front-loaded with the main action.

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?

Tool is simple and description covers basic purpose and effect. However, without annotations or output schema, it would benefit from mentioning return value or prerequisites (e.g., element visibility).

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% and description adds no additional parameter semantics beyond what the schema already provides. The parameter names and descriptions in the schema are sufficient.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the verb 'move mouse' and resource 'element', and distinguishes from sibling 'click' by specifying 'without clicking'. The description is specific and 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?

Implied usage by mentioning 'without clicking', but no explicit guidance on when to use vs alternatives like 'click' or 'drag'. No conditions or exclusions provided.

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

Deploy Server

Other Tools