agent-device

Official

Overview Schema Source Related Servers Score Discussions Admin

hover

Move the pointer over a UI element to reveal hover-dependent controls, such as toolbars or menus, without clicking. Works exclusively on web platforms; use settle to wait for the resulting UI updates.

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. Times out after 90s; a caller-supplied budget extends it.

Input Schema

TableJSON Schema

Name	Required	Description
`raw`	No	Use raw snapshot data during selector resolution.
`udid`	No	Apple device or simulator UDID; the selector that pins one device when several share a name.
`debug`	No	Enable debug diagnostics.
`depth`	No	Snapshot traversal depth.
`runId`	No	Lease run identifier.
`scope`	No	Snapshot scope selector used before resolution.
`device`	No	Device name selector (a UDID belongs in udid, a serial in serial).
`serial`	No	Android, HarmonyOS, or Vega VVD serial selector.
`settle`	No	After 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.
`target`	Yes	UI target. This is separate from deviceTarget, which selects the device form.
`tenant`	No	Remote tenant identifier.
`leaseId`	No	Existing lease identifier.
`session`	No	Agent-device session name.
`noRecord`	No	Do not record this action.
`platform`	No	Platform selector used to resolve a device.
`timeoutMs`	No	Settle: wait deadline in milliseconds (default 10000).
`includeCost`	No	Include per-command agent-cost (cost.wallClockMs, …) in structuredContent. Defaults to off; the default response shape is unchanged.
`deviceTarget`	No	Device target form. Maps to the CLI --target flag.
`responseLevel`	No	Response verbosity: token-cheap digest / default (today) / full. Defaults to default; the default response shape is unchanged.
`settleQuietMs`	No	Settle: quiet window in milliseconds (default 500).
`mcpOutputFormat`	No	MCP text content format. Defaults to optimized agent-friendly text; use json for JSON text. Structured content is always returned separately.
`androidDeviceAllowlist`	No	Android serial allowlist used for device resolution.

Output Schema

TableJSON Schema

Name	Required	Description
`x`	No	Resolved interaction x coordinate when available.
`y`	No	Resolved interaction y coordinate when available.
`ref`	No	Snapshot ref without the @ prefix when the target was an @ref.
`cost`	No
`hint`	No
`settle`	No
`gesture`	No
`message`	No
`warning`	No
`evidence`	No
`refLabel`	No
`selector`	No	Selector expression when the target was a selector.
`resolution`	No	Pre-action disclosure of how the acting path resolved its target. Absent when resolutionDisclosure is inapplicable for the path.
`targetKind`	Yes	Resolved interaction target kind.
`selectorChain`	No
`referenceWidth`	No	Reference frame width for visualizing the interaction point.
`targetHittable`	No
`referenceHeight`	No	Reference frame height for visualizing the interaction point.
`maestroFallbackReason`	No
`maestroNonHittableCoordinateFallbackUsed`	No	Whether the direct iOS Maestro coordinate fallback was actually used.
`maestroNonHittableCoordinateFallbackAllowed`	No	Whether the direct iOS Maestro coordinate fallback was allowed for this selector.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.21.0Sep 9, 2026

changedInput schema / properties / device / description

Previous value: -"Device name selector."New value: +"Device name selector (a UDID belongs in udid, a serial in serial)."

changedInput schema / properties / serial / description

Previous value: -"Android device or Vega VVD serial selector."New value: +"Android, HarmonyOS, or Vega VVD serial selector."

changedInput schema / properties / udid / description

Previous value: -"iOS device UDID selector."New value: +"Apple device or simulator UDID; the selector that pins one device when several share a name."

Changed8 schema fields changedv0.20.10Aug 26, 2026

removedInput schema / properties / cwd

Removed value: -{
-  "description": "Working directory for command execution.",
-  "type": "string"
-}

removedInput schema / properties / daemonAuthToken

Removed value: -{
-  "description": "Remote daemon auth token.",
-  "type": "string"
-}

removedInput schema / properties / daemonBaseUrl

Removed value: -{
-  "description": "Remote daemon base URL.",
-  "type": "string"
-}

removedInput schema / properties / iosSimulatorDeviceSet

Removed value: -{
-  "description": "iOS simulator device-set path used for device resolution.",
-  "type": "string"
-}

removedInput schema / properties / iosXctestDerivedDataPath

Removed value: -{
-  "description": "Derived data path for external iOS XCTest runner execution.",
-  "type": "string"
-}

removedInput schema / properties / iosXctestEnvDir

Removed value: -{
-  "description": "Writable directory for iOS XCTest runner env overlays.",
-  "type": "string"
-}

removedInput schema / properties / iosXctestrunFile

Removed value: -{
-  "description": "Externally built iOS XCTest runner .xctestrun artifact path.",
-  "type": "string"
-}

removedInput schema / properties / stateDir

Removed value: -{
-  "description": "Agent-device state directory.",
-  "type": "string"
-}

Addedv0.20.9Aug 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and provides several useful behavioral facts: the action does not press, it is Web-only, it times out after 90 seconds, and a caller budget can extend it. It does not cover failure modes or side effects in depth, but the main operational traits are disclosed.

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?

Three dense sentences, front-loaded with the action and purpose, followed by platform limitation and timeout. No filler or redundant restating of the schema.

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?

The tool is complex with 22 parameters, but schema coverage is complete and an output schema exists, so the description can focus on behavior. It covers the core action, platform constraint, settle behavior, and timeout. It is not exhaustive about edge cases, but it is complete enough for an agent to invoke it correctly.

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's reference to 'snapshot ref, selector, or coordinates' summarizes the target variants and the settle advice adds a little context, but it does not add meaning beyond what the schema already provides for the 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 names a specific verb ('Move the pointer'), a resource ('a UI target'), three addressing modes (snapshot ref, selector, coordinates), and the purpose ('reveal hover-gated UI'). The 'without pressing' and 'Web only' clauses distinguish it from click/press and from touch-only interactions, so an agent can differentiate it from sibling tools.

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?

It gives a clear use case (hover-gated UI) and an explicit platform exclusion ('Web only; touch platforms have no hover state'). It also tells the agent to use settle to observe results. It does not explicitly name an alternative sibling such as click/press for the 'without pressing' case, so the guidance is clear but not exhaustive.

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

Install Server