Skip to main content
Glama
callstack

agent-device

Official
by callstack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gesture

Perform a structured pan, fling, swipe, pinch, rotate, transform, tap, or drag gesture. Select the gesture kind, then provide only the inputs that apply to that kind. A tap touches 2 to 5 points at once; repeat it with count and pauseMs.

Instructions

Perform a structured pan, fling, swipe, pinch, rotate, transform, tap, or drag gesture. Select the gesture kind, then provide only the inputs that apply to that kind. A tap touches 2 to 5 points at once; repeat it with count and pauseMs. Times out after 90s.

Input Schema

NameRequiredDescriptionDefault
kindYesGesture variant.
udidNoApple device or simulator UDID; the selector that pins one device when several share a name.
countNoTap repetitions; the same contacts run this many times.
debugNoEnable debug diagnostics.
deltaNoMovement delta for pan or transform gestures.
runIdNoLease run identifier.
scaleNoPinch or transform scale.
deviceNoDevice name selector (a UDID belongs in udid, a serial in serial).
holdMsNoTap contact hold duration.
moveMsNoDrag movement duration.
originNoGesture origin point.
pointsNoTap contact points, held together for holdMs.
presetNoSwipe preset.
serialNoAndroid, HarmonyOS, or Vega VVD serial selector.
sourceNoDrag source @ref or selector.
targetNoAlias for deviceTarget on commands without a UI target field. Interaction commands reserve target for the UI element.
tenantNoRemote tenant identifier.
degreesNoRotation in degrees.
leaseIdNoExisting lease identifier.
pauseMsNoDelay between tap repetitions, added to each repetition’s own time.
sessionNoAgent-device session name.
distanceNoFling distance.
noRecordNoDo not record this action.
platformNoPlatform selector used to resolve a device.
directionNoFling direction.
durationMsNoPan/transform duration.
destinationNoDrag destination @ref or selector.
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.
pointerCountNoPan touch pointer count (1 or 2).
sourceHoldMsNoDrag activation hold duration.
responseLevelNoResponse verbosity: token-cheap digest / default (today) / full. Defaults to default; the default response shape is unchanged.
mcpOutputFormatNoMCP text content format. Defaults to optimized agent-friendly text; use json for JSON text. Structured content is always returned separately.
destinationHoldMsNoHold before releasing at the destination.
androidDeviceAllowlistNoAndroid serial allowlist used for device resolution.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.21.29
    • addedInput schema / properties / count
      Added value: +{
+  "description": "Tap repetitions; the same contacts run this many times.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / holdMs
      Added value: +{
+  "description": "Tap contact hold duration.",
+  "maximum": 10000,
+  "minimum": 16,
+  "type": "integer"
+}
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "pan",
-  "fling",
-  "swipe",
-  "pinch",
-  "rotate",
-  "transform",
-  "drag"
-]New value: +[
+  "pan",
+  "fling",
+  "swipe",
+  "pinch",
+  "rotate",
+  "transform",
+  "tap",
+  "drag"
+]
    • addedInput schema / properties / pauseMs
      Added value: +{
+  "description": "Delay between tap repetitions, added to each repetition’s own time.",
+  "maximum": 10000,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / points
      Added value: +{
+  "description": "Tap contact points, held together for holdMs.",
+  "items": {
+    "additionalProperties": false,
+    "description": "One contact point.",
+    "properties": {
+      "x": {
+        "type": "number"
+      },
+      "y": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "x",
+      "y"
+    ],
+    "type": "object"
+  },
+  "maxItems": 5,
+  "minItems": 2,
+  "type": "array"
+}
  2. Changed3 schema fields changedv0.21.0
    • 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."
  3. Changed8 schema fields changedv0.20.10
    • 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"
-}
  4. Changed1 schema field changedv0.20.9
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "apple",
-  "android",
-  "vega",
-  "linux",
-  "web",
-  "ios",
-  "macos"
-]New value: +[
+  "apple",
+  "android",
+  "harmonyos",
+  "vega",
+  "linux",
+  "web",
+  "ios",
+  "macos"
+]
  5. Changed6 schema fields changedv0.20.6
    • 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"
+}
  6. Changed8 schema fields changedv0.20.2
    • 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"
-}
  7. Changed3 schema fields changedv0.17.11
    • 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"
+}
  8. Changed1 schema field changedv0.17.7
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "ios",
-  "macos",
-  "android",
-  "linux",
-  "apple"
-]New value: +[
+  "ios",
+  "macos",
+  "android",
+  "linux",
+  "web",
+  "apple"
+]
  9. Changed5 schema fields changedv0.17.6
    • 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"
+]
  10. First observedv0.16.9

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does contribute two genuinely useful behavioral facts: a hard 90s timeout and the constraint that a tap spans 2–5 simultaneous contacts. It says nothing about whether the action is recorded (despite a noRecord parameter), what happens on failure, or whether a device lease/session must already exist — significant omissions for a 35-parameter interaction tool.

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 short sentences, front-loaded with the verb and the kind enumeration. Every sentence adds a distinct fact — kind selection, tap semantics, and the timeout — with no filler or restatement of the schema.

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

Completeness3/5

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

No output schema exists, so the description is not obliged to explain return values, and the tap and timeout notes cover the trickiest bits. However, for a tool with 35 parameters spanning device selectors, sessions, leases, and response-format flags, the description says nothing about device targeting, prerequisite state, or response behavior, leaving real gaps.

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 100%, so the baseline would be 3, but the description adds value the schema cannot: it establishes that parameters are conditional on kind rather than a flat bag of 35 inputs, and it explains the tap-specific pairing of points with count and pauseMs. It could have gone further by mapping other param groups (preset/direction/distance, scale/degrees) to their kinds, which the schema only partly does.

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 and enumerates all eight gesture kinds, so the resource and its scope are unmistakable. It never distinguishes itself from sibling tools like swipe, longpress, or scroll that overlap with at least three of those kinds, leaving an agent to guess which one to pick.

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?

"Select the gesture kind, then provide only the inputs that apply to that kind" gives real intra-tool guidance on how to drive the schema, and the tap sentence clarifies repetition semantics. But there is no when-to-use framing against the obvious alternatives (swipe, longpress, scroll, click) and no mention of prerequisites such as an active session or lease, so usage is only implied.

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

Deploy Server

Other Tools