agent-device

Official

Overview Schema Related Servers Score Discussions

hover

Move the pointer over a UI target identified by snapshot ref, selector, or coordinates to reveal hidden controls such as row toolbars or menus. Use settle to observe revealed UI.

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	iOS device UDID selector.
`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.
`serial`	No	Android device 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. Dates show when Glama detected each change.

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.5/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and it uses the space well: it clarifies that the pointer moves 'without pressing', that the behavior is Web-only, that the operation times out after 90s, and that a caller-supplied budget can extend it. It also explains the settle behavior as best-effort observation.

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 sentences with no filler; the core action and purpose are front-loaded, followed by the essential platform constraint, workflow hint, and timeout behavior. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 22 parameters and no annotations, the description covers the key operational facts an agent needs: how to target the element, why to use hover, when it is unavailable, how to observe the result, and the timeout bound. The rich schema and output schema cover the remaining details, so nothing critical is missing.

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% with all 22 parameters described, so the baseline is 3. The description adds a high-level mapping to target modes and mentions settle and timeout, but it does not add parameter-level detail beyond what the input schema already provides.

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 and resource ('Move the pointer over a UI target') and exactly how targeting can be supplied ('snapshot ref, selector, or coordinates'). It also states the reason for the action ('reveal hover-gated UI') and the platform limit ('Web only'), which distinguishes hover from click/press siblings.

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 clear when-to-use context: reveal hover-gated UI such as row toolbars or menus, and it excludes non-web/touch platforms ('touch platforms have no hover state'). It also suggests using settle to observe the result without a follow-up snapshot, but it does not explicitly name sibling alternatives such as click or press as the alternative for actual activation.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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