Skip to main content
Glama

Robot Actions — Remote Device Control

by com.robotactions.test
OverviewDiscussionsAdmin

ios_swipe

Swipe from (x1,y1) to (x2,y2) on an iOS device screen. Coordinates are in physical screen points. (On an Apple TV, use ios_tv_button arrows or ios_tv_swipe to move focus — a coordinate swipe is unavailable there.) Requires an active iOS automation session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
x1YesStart X coordinate
x2YesEnd X coordinate
y1YesStart Y coordinate
y2YesEnd Y coordinate
normNoIf 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.
udidYesiOS device UDID
inputNoInput 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.
durationNoSwipe duration in ms (default: 500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden; it usefully reveals the coordinate system ('physical screen points'), the Apple TV limitation, and the session prerequisite. However, it is not complete: it states an active session is required without mentioning the input='hid' path that can bypass the automation session, and it says nothing about default duration or failure behavior.

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 compact sentences front-load the action, then coordinate semantics, platform caveat, and prerequisite. Every sentence contributes either a decision rule or a required precondition, with no repetition of schema content.

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?

The description plus exhaustive parameter descriptions cover the main call decisions: gesture type, coordinate semantics, Apple TV alternative, and session prerequisite. It omits the HID input exception and any return/result info, but for an action tool with a well-documented schema this is a minor gap.

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, and the description adds value by explaining that x/y values are in physical screen points, clarifying the coordinate params and the norm param's default context. It doesn't restate each parameter, but it supplies meaning the schema doesn't fully convey for default behavior.

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 gesture ('Swipe') and target ('iOS device screen') with start/end coordinates, so the action is unambiguous. It also distinguishes itself from ios_tv_swipe by noting coordinate swipes are unavailable on Apple TV, which separates it from an otherwise similar sibling.

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?

Includes an explicit when-not: on Apple TV, use ios_tv_button arrows or ios_tv_swipe instead. Adds a hard prerequisite ('Requires an active iOS automation session') that tells the agent when the call is executable. This is stronger guidance than most sibling definitions.

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 toolsInspect
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