Robot Actions — Remote Device Control

ios_two_finger_swipe

Two-finger swipe from (x1,y1) to (x2,y2) on an iOS device — a two-finger scroll/pan. Both fingers travel the vector in parallel, offset perpendicular to it so one never runs through the other. Use where a one-finger swipe does the wrong thing: tilting a map into 3D, scrolling inside a web view that pans with one finger, or dismissing a two-finger-aware sheet. Coordinates are screen points. Requires an active iOS automation session.

Input Schema

TableJSON Schema

Name	Required	Description
`x1`	Yes	Start X (screen points)
`x2`	Yes	End X (screen points)
`y1`	Yes	Start Y (screen points)
`y2`	Yes	End Y (screen points)
`norm`	No	If true, x/y (and path points) are 0..1 FRACTIONS of the screen — pass `pixelInScreenshot ÷ screenshotSize` directly (scale-free, matches the frontend, avoids point-guessing). Default false = iOS screen points.
`udid`	Yes	iOS device UDID
`input`	No	Input path. 'auto' (default) drives the gesture through the automation session. 'hid' drives it through the direct input path instead, which needs no automation session — it reports 'no HID available' on iOS 17.x or with no tunnel.
`durationMs`	No	Gesture duration in ms (default: 400)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 17, 2026

addedInput schema / properties / input

Added value: +{
+  "description": "Input path. 'auto' (default) drives the gesture through the automation session. 'hid' drives it through the direct input path instead, which needs no automation session — it reports 'no HID available' on iOS 17.x or with no tunnel.",
+  "enum": [
+    "auto",
+    "hid"
+  ],
+  "type": "string"
+}

addedInput schema / properties / norm

Added value: +{
+  "description": "If true, x/y (and path points) are 0..1 FRACTIONS of the screen — pass `pixelInScreenshot ÷ screenshotSize` directly (scale-free, matches the frontend, avoids point-guessing). Default false = iOS screen points.",
+  "type": "boolean"
+}

AddedSep 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description carries full disclosure responsibility. It explains the physical gesture behavior (both fingers travel the vector in parallel, offset perpendicular so they don't run through each other), states that coordinates are screen points, and calls out the session prerequisite. It doesn't cover failure modes or return/status behavior, but for a gesture tool the core behavioral traits are transparently documented.

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 sentences carry all essential information: what the tool does, when to use it, coordinate semantics, and prerequisite. There is no filler or repetition, and the most decision-relevant content (purpose and usage conditions) is front-loaded.

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 gesture tool with no output schema, the combination of description and parameter-rich schema covers purpose, usage conditions, prerequisites, and coordinate system. Minor gaps remain: return/status behavior is not described, and there is no direct pointer to the related ios_two_finger_tap sibling, but the name and examples make the tool's role sufficiently clear.

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 baseline is 3. The description adds the coordinate-semantics note 'Coordinates are screen points' and explains finger geometry, but the schema already documents each coordinate and the norm parameter in detail. The description does not materially improve parameter understanding beyond what the schema provides.

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 precise definition: a two-finger swipe from (x1,y1) to (x2,y2) on an iOS device, explicitly identified with two-finger scroll/pan. It distinguishes itself from one-finger swipes by naming concrete scenarios where a one-finger swipe would be wrong, which effectively separates it from sibling swipe tools 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 Guidelines5/5

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

The description gives explicit when-to-use guidance: 'Use where a one-finger swipe does the wrong thing', followed by three concrete examples (tilting a map into 3D, scrolling inside a one-finger-panning web view, dismissing a two-finger-aware sheet). It also states a hard prerequisite, 'Requires an active iOS automation session', which is essential for correct invocation.

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?