Robot Actions — Remote Device Control

Device swipe

device_swipe

Swipe from (x1,y1) to (x2,y2) on a device screen. Coordinates are PHYSICAL pixels — same as the bounds in device_page_source (no scaling needed).Pass input="hid" to require the virtual touchscreen: the gesture then reaches the app as real kernel input and fails loudly instead of silently falling back to injected input. That strict path used to be device_uhid_swipe, which stays callable under its old name.

Input Schema

TableJSON Schema

Name	Required	Description
`x1`	Yes	Start X coordinate
`x2`	Yes	End X coordinate
`y1`	Yes	Start Y coordinate
`y2`	Yes	End Y coordinate
`udid`	Yes	Device serial number (UDID)
`input`	No	Input path. 'auto' (default) prefers the virtual touchscreen and falls back to injected input. 'hid' requires the virtual touchscreen and fails if the device does not provide one — use it when the gesture must be real kernel input or must fail loudly.
`duration`	No	Swipe duration in ms (default: 500)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedInput schema / properties / input / description

Previous value: -"Input path. 'auto' (default) prefers the virtual touchscreen and falls back to injected input. 'hid' requires the virtual touchscreen and fails if the device does not provide one â use it when the gesture must be real kernel input or must fail loudly."New value: +"Input path. 'auto' (default) prefers the virtual touchscreen and falls back to injected input. 'hid' requires the virtual touchscreen and fails if the device does not provide one — use it when the gesture must be real kernel input or must fail loudly."

Changed1 schema field changedSep 20, 2026

changedInput schema / properties / input / description

Previous value: -"Input path. 'auto' (default) prefers the virtual touchscreen and falls back to injected input. 'hid' requires the virtual touchscreen and fails if the device does not provide one — use it when the gesture must be real kernel input or must fail loudly."New value: +"Input path. 'auto' (default) prefers the virtual touchscreen and falls back to injected input. 'hid' requires the virtual touchscreen and fails if the device does not provide one â use it when the gesture must be real kernel input or must fail loudly."

Changed1 schema field changedSep 17, 2026

addedInput schema / properties / input

Added value: +{
+  "description": "Input path. 'auto' (default) prefers the virtual touchscreen and falls back to injected input. 'hid' requires the virtual touchscreen and fails if the device does not provide one — use it when the gesture must be real kernel input or must fail loudly.",
+  "enum": [
+    "auto",
+    "hid"
+  ],
+  "type": "string"
+}

First observedAug 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the annotations (readOnly false, destructive false, idempotent false), the description discloses two behavioral traits: the default 'auto' path silently falls back to injected input, while 'hid' fails loudly, and the legacy device_uhid_swipe alias still works. It omits any auth/permission prerequisites, but adds real context the annotations do not.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and coordinate semantics in the first two sentences, then the input-path nuance. The final sentence about the old device_uhid_swipe name is borderline but useful for routing agents holding stale tool names.

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?

With 100% schema coverage, annotations covering the safety profile, and no output schema to explain, the description closes the remaining gaps an agent needs: coordinate units, the default-vs-strict input behavior, and the alias. Nothing required to invoke it correctly is missing.

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, but the description adds value the schema lacks: x/y values are physical pixels matching device_page_source bounds with no scaling, and it explains the intent behind the input enum values ('fails loudly instead of silently falling back').

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Swipe ... on a device screen") and pins the coordinate system to physical pixels. However, it does not distinguish this tool from close siblings like device_drag_drop or device_gesture_path, so an agent must infer the boundary from the name alone.

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?

It states an explicit condition for the strict path (pass input="hid" when the gesture must be real kernel input or must fail loudly), which is genuine usage guidance. It stops short of saying when to choose device_swipe over device_drag_drop, device_scroll, or device_uhid_input.

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

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?