Robot Actions — Remote Device Control

ios_reboot

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?

With no annotations, the description carries full responsibility for behavioral disclosure. It thoroughly warns that the operation is disruptive, non-reversible, causes ~1 minute unreachability, drops the session and stream, and loses in-progress work. It also states the mandatory confirm=true requirement, covering all critical consequences.

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?

Every sentence earns its place: purpose, disruption warning, confirm requirement, anti-pattern, correct usage condition, and sibling differentiation. It is front-loaded with the core action and warning, then context, with no fluff or redundancy.

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 destructive tool with no annotations and no output schema, the description covers everything an agent needs: when to use, consequences, prerequisite (no session needed), and the alternative. It is fully self-contained and leaves no gap in calling the tool correctly.

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 fully documented in the input schema, including the const: true constraint on confirm. The description reiterates the confirm requirement but adds little beyond the schema—it doesn't clarify udid further. Baseline 3 is appropriate since schema already does the heavy lifting.

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 opens with a specific verb and resource: 'Reboot an iOS device.' It clearly distinguishes itself from siblings by naming ios_end_session as the alternative for session resets and device_reboot as the Android counterpart, making its unique purpose unmistakable.

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?

Explicit when-to-use and when-not-to-use guidance is provided: 'Do NOT reach for this to recover from a flaky tool call; try ios_end_session first' and 'Reboot only when the device itself is wedged and a human has asked for it.' It also notes that no automation session is required, fully routing the agent.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?