agent-device

Official

by callstack

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

gesture

Execute touch gestures like swipe, pinch, and drag on mobile, TV, or desktop devices to simulate user interactions.

Instructions

Perform a structured pan, fling, swipe, pinch, rotate, transform, or drag gesture. Select the gesture kind, then provide only the inputs that apply to that kind. Times out after 90s.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes	Gesture variant.
`udid`	No	Apple device or simulator UDID; the selector that pins one device when several share a name.
`debug`	No	Enable debug diagnostics.
`delta`	No	Movement delta for pan or transform gestures.
`runId`	No	Lease run identifier.
`scale`	No	Pinch or transform scale.
`device`	No	Device name selector (a UDID belongs in udid, a serial in serial).
`moveMs`	No	Drag movement duration.
`origin`	No	Gesture origin point.
`preset`	No	Swipe preset.
`serial`	No	Android, HarmonyOS, or Vega VVD serial selector.
`source`	No	Drag source @ref or 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.
`degrees`	No	Rotation in degrees.
`leaseId`	No	Existing lease identifier.
`session`	No	Agent-device session name.
`distance`	No	Fling distance.
`noRecord`	No	Do not record this action.
`platform`	No	Platform selector used to resolve a device.
`direction`	No	Fling direction.
`durationMs`	No	Pan/transform duration.
`destination`	No	Drag destination @ref or selector.
`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.
`pointerCount`	No	Pan touch pointer count (1 or 2).
`sourceHoldMs`	No	Drag activation hold duration.
`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.
`destinationHoldMs`	No	Hold before releasing at the destination.
`androidDeviceAllowlist`	No	Android serial allowlist used for device resolution.

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

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"
+]

Changed6 schema fields changedv0.20.6Aug 7, 2026

addedInput schema / properties / destination

Added value: +{
+  "description": "Drag destination @ref or selector.",
+  "type": "string"
+}

addedInput schema / properties / destinationHoldMs

Added value: +{
+  "description": "Hold before releasing at the destination.",
+  "maximum": 10000,
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / kind / enum

Previous value: -[
-  "pan",
-  "fling",
-  "swipe",
-  "pinch",
-  "rotate",
-  "transform"
-]New value: +[
+  "pan",
+  "fling",
+  "swipe",
+  "pinch",
+  "rotate",
+  "transform",
+  "drag"
+]

addedInput schema / properties / moveMs

Added value: +{
+  "description": "Drag movement duration.",
+  "maximum": 10000,
+  "minimum": 16,
+  "type": "integer"
+}

addedInput schema / properties / source

Added value: +{
+  "description": "Drag source @ref or selector.",
+  "type": "string"
+}

addedInput schema / properties / sourceHoldMs

Added value: +{
+  "description": "Drag activation hold duration.",
+  "maximum": 10000,
+  "minimum": 1,
+  "type": "integer"
+}

Changed8 schema fields changedv0.20.2Jul 30, 2026

changedInput schema / properties / durationMs / description

Previous value: -"Gesture duration in milliseconds."New value: +"Pan/transform duration."

addedInput schema / properties / durationMs / maximum
```
Added value: +10000
```
changedInput schema / properties / durationMs / minimum
```
Previous value: -0New value: +16
```

addedInput schema / properties / noRecord

Added value: +{
+  "description": "Do not record this action.",
+  "type": "boolean"
+}

changedInput schema / properties / platform / enum

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

addedInput schema / properties / pointerCount

Added value: +{
+  "description": "Pan touch pointer count (1 or 2).",
+  "maximum": 2,
+  "minimum": 1,
+  "type": "integer"
+}

changedInput schema / properties / serial / description

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

removedInput schema / properties / velocity

Removed value: -{
-  "description": "Rotate gesture velocity.",
-  "minimum": 0,
-  "type": "integer"
-}

Changed3 schema fields changedv0.17.11Jul 6, 2026

addedInput schema / properties / includeCost

Added value: +{
+  "description": "Include per-command agent-cost (cost.wallClockMs, …) in structuredContent. Defaults to off; the default response shape is unchanged.",
+  "type": "boolean"
+}

changedInput schema / properties / platform / enum

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

addedInput schema / properties / responseLevel

Added value: +{
+  "description": "Response verbosity: token-cheap digest / default (today) / full. Defaults to default; the default response shape is unchanged.",
+  "enum": [
+    "digest",
+    "default",
+    "full"
+  ],
+  "type": "string"
+}

Changed1 schema field changedv0.17.7Jun 23, 2026

changedInput schema / properties / platform / enum

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

Changed5 schema fields changedv0.17.6Jun 18, 2026

addedInput schema / properties / iosXctestDerivedDataPath

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

addedInput schema / properties / iosXctestEnvDir

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

addedInput schema / properties / iosXctestrunFile

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

addedInput schema / properties / mcpOutputFormat

Added value: +{
+  "description": "MCP text content format. Defaults to optimized agent-friendly text; use json for JSON text. Structured content is always returned separately.",
+  "enum": [
+    "optimized",
+    "json"
+  ],
+  "type": "string"
+}

changedInput schema / properties / platform / enum

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

First observedv0.16.9Jun 3, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must carry full burden. It discloses a 90s timeout, which is a useful behavioral trait. However, it does not mention side effects, whether it is read-only or destructive, or any other behaviors. The term 'structured' is vague and does not clarify what the tool does beyond performing the gesture. It does not mention recording or device targeting. Given the lack of annotations, this is insufficient.

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?

The description is a single sentence that states the purpose and a usage rule, plus a timeout. It is concise and front-loads the purpose. However, it could be structured to list the kinds more clearly. Still, it is appropriately sized.

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

Completeness2/5

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

For a tool with 31 parameters and 7 gesture kinds, the description is extremely sparse. It does not explain which parameters apply to which gesture kind, nor does it describe the output. With no output schema, the description should clarify what the tool returns, but it does not. The schema has parameter descriptions, but they are not enough to understand the gesture-specific requirements. The description is far from complete for such a complex tool.

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 the baseline is 3. The description adds the rule to provide only inputs that apply to the selected kind, which gives a generic guideline. It does not add specific parameter details beyond what the schema provides. It adds minimal value.

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?

The description clearly states it performs a structured gesture of various types (pan, fling, swipe, pinch, rotate, transform, drag). However, it does not differentiate from sibling tools like the dedicated 'swipe' tool, which could confuse an agent about which tool to use. The purpose is explicit but sibling differentiation is weak.

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

Usage Guidelines2/5

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

The description says to select the gesture kind and provide only applicable inputs, but it does not specify when to use this tool versus alternatives like swipe or scroll. No exclusions or context about scenarios are given. It offers minimal guidance on usage.

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

Deploy Server

gesture

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools