agent-device

Official

Overview Schema Source Related Servers Discussions Admin

orientation

Control screen rotation on iOS and Android devices, and return ADB-backed Android devices to sensor-driven auto rotation.

Instructions

Set device orientation on iOS and Android. auto hands rotation back to the sensor on ADB-backed Android (local and Limrun); other backends refuse it. A foldable iPhone simulator (iPhone Duo) refuses portrait-upside-down, and refuses every rotation in a scoped simulator set. Times out after 90s.

Input Schema

Name	Required	Description
`udid`	No	Apple device or simulator UDID; the selector that pins one device when several share a name.
`debug`	No	Enable debug diagnostics.
`runId`	No	Lease run identifier.
`device`	No	Device name selector (a UDID belongs in udid, a serial in serial).
`serial`	No	Android, HarmonyOS, or Vega VVD serial selector.
`target`	No	Alias for deviceTarget on commands without a UI target field. Interaction commands reserve target for the UI element.
`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.
`includeCost`	No	Include per-command agent-cost (cost.wallClockMs, …) in structuredContent. Defaults to off; the default response shape is unchanged.
`orientation`	Yes
`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.
`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

Name	Required	Description	Default
`action`	Yes
`message`	Yes
`warning`	No
`confirmed`	No
`orientation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.21.29Oct 23, 2026

changedInput schema / properties / orientation / enum

Previous value: -[
-  "portrait",
-  "portrait-upside-down",
-  "landscape-left",
-  "landscape-right"
-]New value: +[
+  "portrait",
+  "portrait-upside-down",
+  "landscape-left",
+  "landscape-right",
+  "auto"
+]

changedOutput schema / properties / orientation / enum

Previous value: -[
-  "portrait",
-  "portrait-upside-down",
-  "landscape-left",
-  "landscape-right"
-]New value: +[
+  "portrait",
+  "portrait-upside-down",
+  "landscape-left",
+  "landscape-right",
+  "auto"
+]

Changed2 schema fields changedv0.21.2Sep 16, 2026
- addedOutput schema / properties / confirmed
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / warning
```
Added value: +{
+  "type": "string"
+}
```

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"
-}

Changed1 schema field changedv0.20.9Aug 19, 2026

changedInput schema / properties / platform / enum

Previous value: -[
-  "apple",
-  "android",
-  "vega",
-  "linux",
-  "web",
-  "ios",
-  "macos"
-]New value: +[
+  "apple",
+  "android",
+  "harmonyos",
+  "vega",
+  "linux",
+  "web",
+  "ios",
+  "macos"
+]

Addedv0.20.2Jul 30, 2026

TDQS

A3.8/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 load and does well: it discloses that 'auto' only works on ADB-backed Android (local and Limrun) and that other backends refuse it, that iPhone Duo refuses portrait-upside-down, that scoped simulator sets refuse all rotations, and a 90s timeout. Missing are permission/session prerequisites and whether failures surface as errors vs silent no-ops.

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?

Three dense sentences, front-loaded with the action and followed by the platform exceptions and the timeout. Every sentence carries information, though the parenthetical '(local and Limrun)' and 'scoped simulator set' are compressed to the point of being cryptic on first read.

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?

An output schema exists and 94% of parameters are documented, so the description only needs to supply behavior — which it does for the platform-specific refusals and the timeout. One gap: the schema's platform enum includes harmonyos, vega, linux, web, and macos, while the description frames the tool as iOS/Android only, leaving the agent unsure how those platforms behave.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 94%, so the baseline is 3; the description earns a notch above by explaining the non-obvious runtime semantics of a specific enum value ('auto' hands rotation back to the sensor, and only on ADB-backed Android). It adds nothing for the many device-selector parameters, but those are already documented in the schema.

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?

Opens with a specific verb+resource: 'Set device orientation on iOS and Android', which immediately tells an agent what the tool does. It doesn't distinguish itself from related siblings like fold, viewport, or settings, but the caveats that follow are specific enough to pin the tool down.

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

Usage Guidelines3/5

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

Implied usage is clear (change rotation), but there is no explicit 'use this instead of X' or when-not guidance beyond the per-backend caveats. The 'auto' restriction is framed as a constraint, not as routing advice, and no alternative tool is named.

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

Deploy Server