Robot Actions — Remote Device Control

ios_pinch

Two-finger pinch-to-zoom centred at (x,y) on an iOS device. scale > 1 zooms IN (fingers spread), scale < 1 zooms OUT (fingers converge); ~2 doubles, ~0.5 halves. Both fingers ride a vertical axis through the centre and are auto-clamped on-screen. Use on Maps, Photos, Safari, camera. Coordinates are screen points. Requires an active iOS automation session.

Input Schema

TableJSON Schema

Name	Required	Description
`x`	Yes	Pinch centre X (screen points)
`y`	Yes	Pinch centre 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.
`scale`	Yes	End/start finger-separation ratio: >1 zoom in, <1 zoom out (0.2–5)
`durationMs`	No	Gesture duration in ms (default: 250)

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

First observedAug 4, 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 the full burden. It discloses several behavioral traits: fingers ride a vertical axis, auto-clamped on-screen, requires an active iOS automation session, and the input path behavior is partially covered in the schema. It doesn't mention what happens on failure or whether the gesture is blocking, but the disclosed details are meaningful and go beyond the schema.

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 compact and front-loaded: it opens with the core action and center point, then explains scale direction, then finger behavior, then use cases, then coordinate system, then session requirement. Every sentence carries information 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 gesture tool with 7 parameters and no output schema, the description covers the essential behavioral context: scale direction, coordinate system, clamping, and session requirement. It doesn't explain the 'norm' parameter's relationship to screenshots or the 'input' parameter's HID caveat in the description, but the schema already documents those. The description is complete enough for an agent to invoke it correctly.

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 coverage is 100%, so the baseline is 3. The description adds value by explaining the scale semantics ('~2 doubles, ~0.5 halves') and the coordinate system ('screen points'), which reinforces and clarifies the schema. It doesn't add much beyond that, but the scale explanation is genuinely useful for correct invocation.

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 verb ('pinch-to-zoom'), the resource (iOS device), and the exact behavior (centred at x,y, scale >1 zooms in, <1 zooms out). It also names concrete use cases (Maps, Photos, Safari, camera), which distinguishes it from generic gesture tools like device_pinch or ios_swipe.

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 clear context on when to use it ('Use on Maps, Photos, Safari, camera') and explains the coordinate system and session requirement. It doesn't explicitly name alternatives or exclusions, but the use-case list plus the iOS-specific scope makes the intended usage clear enough.

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?