Robot Actions — Remote Device Control

iOS reboot

ios_reboot

Destructive

Reboot an iOS device. DISRUPTIVE and NOT REVERSIBLE: the device is unreachable for roughly a minute, the automation session and the stream go down, and anything in progress on the device is lost. Requires confirm=true — there is no default. Do NOT reach for this to recover from a flaky tool call; try ios_end_session first, which resets the automation session without touching the device. Reboot only when the device itself is wedged and a human has asked for it. No automation session required. The Android counterpart is device_reboot.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`udid`	Yes	iOS device UDID
`confirm`	Yes	Must be exactly true. Acknowledges the device will restart and the session will be lost.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 16, 2026

addedInput schema / properties / confirm

Added value: +{
+  "const": true,
+  "description": "Must be exactly true. Acknowledges the device will restart and the session will be lost.",
+  "type": "boolean"
+}

changedInput schema / required

Previous value: -[
-  "udid"
-]New value: +[
+  "udid",
+  "confirm"
+]

First observedAug 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description goes well beyond them: device unreachable ~1 minute, session and stream drop, in-progress work is lost, and no automation session is required. This is exactly the behavioral context an agent needs before an irreversible action.

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?

Front-loaded with purpose, then a capitalized disruptive/irreversible warning, then routing guidance and the counterpart note. Every sentence carries distinct information with no filler.

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

Completeness5/5

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

For a two-param, no-output-schema destructive tool, the description covers impact, duration, prerequisites (confirm), session requirements, and alternatives. Nothing an agent needs to invoke it safely is missing.

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% and both parameters are documented in the schema, with confirm already const:true and required. The description reinforces that confirm must be set with no default, adding marginal value, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Reboot an iOS device') and explicitly distinguishes itself from siblings by naming ios_end_session and device_reboot. An agent can tell immediately what this does and which tools it is not.

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

Usage Guidelines5/5

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

Gives explicit when-not ('Do NOT reach for this to recover from a flaky tool call'), an alternative with rationale (ios_end_session resets the session without touching the device), and the narrow when-to-use condition (device wedged and a human asked). Nothing is left to inference.

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

All Robot Actions — Remote Device Control tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?