agent-device

Official

Overview Schema Source Related Servers Discussions Admin

shutdown

Shut down a selected simulator or emulator using device identifiers like UDID, serial, or name. Operation times out after 90 seconds.

Instructions

Shutdown a selected simulator or emulator. Times out after 90s.

Input Schema

TableJSON 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.
`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.
`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

TableJSON Schema

Name	Required	Description
`id`	Yes	Stable device id.
`kind`	Yes
`device`	Yes	Human-readable device name.
`target`	Yes
`platform`	Yes
`shutdown`	Yes

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

Changed2 schema fields 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"
+]

changedOutput schema / properties / platform / enum

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

Changed3 schema fields changedv0.20.2Jul 30, 2026

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

changedOutput schema / properties / platform / enum

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

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": {
+    "device": {
+      "description": "Human-readable device name.",
+      "type": "string"
+    },
+    "id": {
+      "description": "Stable device id.",
+      "type": "string"
+    },
+    "kind": {
+      "enum": [
+        "simulator",
+        "emulator",
+        "device"
+      ],
+      "type": "string"
+    },
+    "platform": {
+      "enum": [
+        "apple",
+        "android",
+        "linux",
+        "web"
+      ],
+      "type": "string"
+    },
+    "shutdown": {
+      "properties": {
+        "error": {
+          "additionalProperties": true,
+          "description": "Normalized error detail when shutdown failed.",
+          "type": "object"
+        },
+        "exitCode": {
+          "type": "number"
+        },
+        "stderr": {
+          "type": "string"
+        },
+        "stdout": {
+          "type": "string"
+        },
+        "success": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "success",
+        "exitCode",
+        "stdout",
+        "stderr"
+      ],
+      "type": "object"
+    },
+    "target": {
+      "enum": [
+        "mobile",
+        "tv",
+        "desktop"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "platform",
+    "target",
+    "device",
+    "id",
+    "kind",
+    "shutdown"
+  ],
+  "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"
+]

Addedv0.17.6Jun 18, 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 carries the full burden of behavioral disclosure. It does add a useful timeout fact ('Times out after 90s'), but it does not disclose that this is a destructive operation, what happens to the device's state, whether shutdown is graceful or forced, or what the agent should expect on timeout. This is a meaningful gap for a shutdown command.

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?

The description is two short sentences with no filler. The primary action is front-loaded, and the timeout detail earns its place as a useful operational constraint. It is appropriately sized for a tool whose behavior is simple, even if the parameter surface is large.

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?

With 15 parameters, no annotations, and only a two-sentence description, the context is incomplete. Although the schema documents each parameter and an output schema exists, the description does not explain which selectors are relevant, how the 'selected' device is resolved, or what the shutdown operation entails beyond stopping. An agent would likely need to inspect many sibling tools and parameter descriptions to use it confidently.

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 description coverage is 100%, so the input schema already documents all 15 parameters in detail. The description itself adds no parameter-level meaning, such as which selector (udid, device, serial, platform) is preferred or how to identify the target. Per the baseline rule for high coverage, a 3 is appropriate.

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 states a specific verb ('Shutdown') and a clear resource ('a selected simulator or emulator'), which makes the core action immediately understandable. It does not explicitly differentiate from siblings like 'close' or 'boot', but the action is distinct enough that a well-informed agent can infer the intent.

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?

There is no guidance about when to use shutdown instead of sibling tools such as 'close', 'boot', or 'session'. The phrase 'selected simulator or emulator' implies there is a selection mechanism, but it never explains how the agent should choose this tool over alternatives or under what conditions shutdown is appropriate.

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

Deploy Server

shutdown

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools