Skip to main content
Glama

hover

Move pointer over a UI target to reveal hover-gated elements without pressing. Use on web platforms to inspect hover states.

Instructions

Move the pointer over a UI target by snapshot ref, selector, or coordinates without pressing, to reveal hover-gated UI such as row toolbars or menus. Web only; touch platforms have no hover state. Use settle to observe what the hover revealed without a follow-up snapshot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory for command execution.
rawNoUse raw snapshot data during selector resolution.
udidNoiOS device UDID selector.
debugNoEnable debug diagnostics.
depthNoSnapshot traversal depth.
runIdNoLease run identifier.
scopeNoSnapshot scope selector used before resolution.
deviceNoDevice name selector.
serialNoAndroid device or Vega VVD serial selector.
settleNoAfter the action, wait for the UI to go quiet and return the settled diff vs the pre-action tree in the same response. Best-effort; never fails the action.
targetYesUI target. This is separate from deviceTarget, which selects the device form.
tenantNoRemote tenant identifier.
leaseIdNoExisting lease identifier.
sessionNoAgent-device session name.
noRecordNoDo not record this action.
platformNoPlatform selector used to resolve a device.
stateDirNoAgent-device state directory.
timeoutMsNoSettle: wait deadline in milliseconds (default 10000).
includeCostNoInclude per-command agent-cost (cost.wallClockMs, …) in structuredContent. Defaults to off; the default response shape is unchanged.
deviceTargetNoDevice target form. Maps to the CLI --target flag.
daemonBaseUrlNoRemote daemon base URL.
responseLevelNoResponse verbosity: token-cheap digest / default (today) / full. Defaults to default; the default response shape is unchanged.
settleQuietMsNoSettle: quiet window in milliseconds (default 500).
daemonAuthTokenNoRemote daemon auth token.
iosXctestEnvDirNoWritable directory for iOS XCTest runner env overlays.
mcpOutputFormatNoMCP text content format. Defaults to optimized agent-friendly text; use json for JSON text. Structured content is always returned separately.
iosXctestrunFileNoExternally built iOS XCTest runner .xctestrun artifact path.
iosSimulatorDeviceSetNoiOS simulator device-set path used for device resolution.
androidDeviceAllowlistNoAndroid serial allowlist used for device resolution.
iosXctestDerivedDataPathNoDerived data path for external iOS XCTest runner execution.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoResolved interaction x coordinate when available.
yNoResolved interaction y coordinate when available.
refNoSnapshot ref without the @ prefix when the target was an @ref.
costNo
hintNo
settleNo
gestureNo
messageNo
warningNo
evidenceNo
refLabelNo
selectorNoSelector expression when the target was a selector.
resolutionNoPre-action disclosure of how the acting path resolved its target. Absent when resolutionDisclosure is inapplicable for the path.
targetKindYesResolved interaction target kind.
selectorChainNo
referenceWidthNoReference frame width for visualizing the interaction point.
targetHittableNo
referenceHeightNoReference frame height for visualizing the interaction point.
maestroFallbackReasonNo
maestroNonHittableCoordinateFallbackUsedNoWhether the direct iOS Maestro coordinate fallback was actually used.
maestroNonHittableCoordinateFallbackAllowedNoWhether the direct iOS Maestro coordinate fallback was allowed for this selector.
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses the non-pressing nature of the action, the web-only limitation, and the settle behavior for observing revealed UI. This adds meaningful behavioral context beyond the schema, though it omits failure modes or what happens when a target cannot be resolved.

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?

The description is three sentences with no filler. It front-loads the main action, then adds platform constraints and a practical settle-related tip, making every sentence substantive.

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?

For a tool with 30 parameters and an output schema, the description gives enough context for selection and invocation: the core hover semantics, web-only limitation, and recommended settle workflow. It could additionally mention relationship to click or failure behavior, but these are not essential given the schema and output schema coverage.

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%, so the baseline is 3. The description reinforces that target can be given by ref, selector, or coordinates and that settle returns the settled diff, but it adds little detail beyond what the schema already documents for parameters.

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?

The description clearly states the verb and resource: 'Move the pointer over a UI target' by ref, selector, or coordinates, and explains the purpose: 'to reveal hover-gated UI such as row toolbars or menus.' It distinguishes itself from click/press/focus by emphasizing 'without pressing' and the web-only platform restriction.

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

Usage Guidelines4/5

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

The description gives clear usage context: use hover to reveal hover-gated UI, and notes that touch platforms have no hover state. It also suggests using settle to observe the reveal without a follow-up snapshot. It does not explicitly name sibling alternatives like click or focus, but the 'without pressing' contrast and platform exclusion provide practical guidance.

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/callstack/agent-device'

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