Skip to main content
Glama
Sign In
Free Codin Agent

Free Codin Agent

by office233
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_hover

Destructive

Simulate a mouse hover over a web element by ref, visible text, or CSS selector to trigger hover states and reveal tooltips or menus.

Instructions

Hover over an element.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoElement ref from browser_snapshot, e.g. "e12"
textNoVisible text to match (alternative to ref)
selectorNoCSS or Playwright selector (alternative to ref)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare the safety profile (destructiveHint=true, openWorldHint=true, idempotentHint=false), so the description is not burdened with that. However, it adds nothing beyond them: no mention of whether hovering triggers hover-only UI, side effects, or failures on missing elements. No contradiction with the annotations, just zero added context.

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?

Four words, front-loaded, no filler. It is as concise as possible, though the brevity borders on under-specification.

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 three-optional-param interaction tool with full schema coverage and no output schema, the minimal description is borderline adequate. It omits target-resolution precedence (ref vs text vs selector) and what hovering actually produces, which an agent would benefit from.

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 each of ref, text, and selector documented as alternatives, so the schema carries semantics. The description adds nothing about precedence among the three targeting modes, which is the one thing missing. 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?

States a specific verb and resource: hover over an element. It is distinguishable from the other browser_* tools (click, type, scroll) by its unique action, though it offers no explicit sibling differentiation.

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 hover versus clicking, typing, or waiting, and no note about prerequisites such as having a snapshot ref available. The agent must infer usage entirely from the name.

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