agent-device

Official

Overview Schema Related Servers Score Discussions

back

Move to the previous screen using the app's navigation stack or the platform's system navigation. Choose in-app for app-level flow or system for OS-level behavior.

Instructions

Navigate back in the app or through system navigation. Use in-app for the app navigation stack and system when the platform back behavior is required. Times out after 90s; a caller-supplied budget extends it.

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	No
`udid`	No	iOS device UDID selector.
`debug`	No	Enable debug diagnostics.
`runId`	No	Lease run identifier.
`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`	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.
`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	Default
`mode`	Yes
`action`	Yes
`settle`	No
`message`	Yes

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

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

Changed4 schema fields changedv0.20.6Aug 7, 2026

addedInput schema / properties / settle

Added value: +{
+  "description": "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.",
+  "type": "boolean"
+}

addedInput schema / properties / settleQuietMs

Added value: +{
+  "description": "Settle: quiet window in milliseconds (default 500).",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / timeoutMs

Added value: +{
+  "description": "Settle: wait deadline in milliseconds (default 10000).",
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / settle

Added value: +{
+  "properties": {
+    "captures": {
+      "type": "number"
+    },
+    "diff": {
+      "description": "Settled diff vs the pre-action tree (changed lines only).",
+      "properties": {
+        "lines": {
+          "items": {
+            "properties": {
+              "kind": {
+                "enum": [
+                  "added",
+                  "removed"
+                ],
+                "type": "string"
+              },
+              "ref": {
+                "description": "Plain ref body (e12) for added lines.",
+                "type": "string"
+              },
+              "text": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "kind",
+              "text"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "summary": {
+          "properties": {
+            "additions": {
+              "type": "number"
+            },
+            "removals": {
+              "type": "number"
+            },
+            "unchanged": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "additions",
+            "removals",
+            "unchanged"
+          ],
+          "type": "object"
+        },
+        "truncated": {
+          "description": "Lines were capped to the response bound.",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "summary",
+        "lines"
+      ],
+      "type": "object"
+    },
+    "hint": {
+      "type": "string"
+    },
+    "quietMs": {
+      "type": "number"
+    },
+    "refs": {
+      "items": {
+        "properties": {
+          "ref": {
+            "description": "Plain ref body (e12) minted from the stored settled tree.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "ref"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "refsGeneration": {
+      "description": "Snapshot generation of the stored settled tree; refs on added diff lines were minted from it.",
+      "type": "number"
+    },
+    "settled": {
+      "description": "Whether the UI held the quiet window before the deadline. false is advisory, not failure.",
+      "type": "boolean"
+    },
+    "tail": {
+      "description": "Unchanged interactive refs tail: still-present, actionable elements from the settled tree, attached only when diff carries zero added-line refs (a modal-dismiss/toast-only diff).",
+      "items": {
+        "properties": {
+          "label": {
+            "type": "string"
+          },
+          "ref": {
+            "description": "Plain ref body (e12) minted from the stored settled tree.",
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "ref",
+          "role"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "tailTruncated": {
+      "description": "Present (true) when tail candidates exceeded the response cap.",
+      "type": "boolean"
+    },
+    "timeoutMs": {
+      "type": "number"
+    },
+    "waitedMs": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "settled",
+    "waitedMs",
+    "captures",
+    "quietMs",
+    "timeoutMs"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedv0.20.2Jul 30, 2026

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

changedInput schema / properties / serial / description

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

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "action": {
+      "const": "back",
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "mode": {
+      "enum": [
+        "in-app",
+        "system"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "action",
+    "mode",
+    "message"
+  ],
+  "type": "object"
+}

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

A4.4/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 does disclose a notable behavioral trait: the 90-second timeout and extension via caller-supplied budget. It also clarifies that system mode triggers platform-native back behavior. It could mention side effects like exiting the app, but the provided details are meaningful.

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 tight sentences, each earning its place: the action, the mode-selection guidance, and the timeout behavior. The most important information is front-loaded and there is no filler.

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?

For a navigation command with a rich schema and an output schema, the description covers the core decision (mode choice) and a key behavioral constraint (timeout). It does not discuss device-resolution details or potential exit behavior, but those are less critical for correct invocation given the schema's high coverage.

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 description coverage is 95%, so the baseline is 3, but the description adds real semantic value by explaining the mode parameter's two values: in-app for the app navigation stack and system for platform back behavior. This goes beyond the raw enum and helps the agent pick correctly.

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 states a specific action—'Navigate back in the app or through system navigation'—and clearly distinguishes the two modes it supports. This separates it from sibling navigation tools like home and app-switcher without ambiguity.

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?

The description gives explicit guidance on when to use each mode: in-app for the app navigation stack and system for platform back behavior. It does not name alternative tools like gesture or swipe, but the mode-level guidance is clear and actionable.

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