Skip to main content
Glama

safari_native_hover

Performs OS-level mouse hover to trigger native :hover and mouseenter events on elements that ignore JavaScript-dispatched hover, such as Discord tooltips. Dwells for rendering, then restores cursor.

Instructions

OS-level mouse hover via macOS CGEvent — moves the real cursor to an element to trigger native :hover / mouseenter handlers. Use for obfuscated UIs where JS-dispatched mouseenter isn't enough, like Discord server sidebars (tooltips only appear on real hover) or portal-rendered tooltips. After hover, call safari_wait_for or safari_evaluate to read the tooltip. Dwells for dwellMs to let tooltips render, then restores the original cursor position by default. Requires Safari window to be visible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoRef ID from safari_snapshot
selectorNoCSS selector
textNoVisible text to find and hover
xNoViewport X coordinate
yNoViewport Y coordinate
dwellMsNoMilliseconds to dwell over the element so tooltips render (clamped 0-5000)
restoreMouseNoRestore cursor to original position after dwell
Behavior4/5

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

Discloses key behaviors: real cursor movement, dwell mechanism, cursor restoration, and requirement for visible window. With no annotations, this is thorough, though could mention potential interference with user input.

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?

Four sentences front-loading purpose, then usage, then behavior. No redundant or irrelevant information.

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?

Covers purpose, usage, and key behaviors adequately for a hover tool. Missing return value explanation, but no output schema implies minimal return. Sufficient for intended use.

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%, so baseline is 3. Description adds limited extra meaning beyond the schema (e.g., dwell purpose). No significant semantic enrichment.

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?

Explicitly states 'OS-level mouse hover via macOS CGEvent' and distinguishes from JS hover siblings. Unambiguously describes what tool does.

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

Usage Guidelines5/5

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

Explicitly states when to use (obfuscated UIs, Discord server sidebars) and gives post-hover actions (safari_wait_for or safari_evaluate). Clearly differentiates from JS-based alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/achiya-automation/safari-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server