0bull Phone Farm

Phone Control Tool

phone-control-tool

Destructive

Send one raw input to a farm phone. The phone must show video_live: true in list-phones-tool. Unlike phone-command-tool, which queues a run, input is applied directly and the call returns as soon as the phone acknowledges it. Coordinates are fractions of the screen (0..1: 0 = left/top, 1 = right/bottom). Ops:

tap (fx, fy): tap a point
swipe (fx1, fy1, fx2, fy2, optional steps): drag/flick between two points
hotkey (key): press a key: home, app_switcher, control_center, notifications, back, run_shortcut, enter, backspace, copy, cut, paste, select_all
type (text): type ASCII text into the focused field

Input Schema

TableJSON Schema

Name	Required	Description
`fx`	No	Tap x, fraction 0..1 (for tap). Optional.
`fy`	No	Tap y, fraction 0..1 (for tap). Optional.
`op`	Yes	Input op: tap, swipe, hotkey, type.
`fx1`	No	Swipe start x, fraction 0..1 (for swipe). Optional.
`fx2`	No	Swipe end x, fraction 0..1 (for swipe). Optional.
`fy1`	No	Swipe start y, fraction 0..1 (for swipe). Optional.
`fy2`	No	Swipe end y, fraction 0..1 (for swipe). Optional.
`key`	No	Key name (for hotkey): home, app_switcher, control_center, notifications, back, run_shortcut, enter, backspace, copy, cut, paste, select_all. Optional.
`slot`	Yes	Phone slot to control, given as the `slot` UUID from list-phones-tool (its display name like "slot12" is not accepted). The phone must show `video_live: true` there.
`text`	No	Text to type into the focused field (for type). Optional.
`steps`	No	Swipe step count controlling gesture speed (for swipe). Defaults to 20. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 25, 2026

addedInput schema / properties / key / enum

Added value: +[
+  "home",
+  "app_switcher",
+  "control_center",
+  "notifications",
+  "back",
+  "run_shortcut",
+  "enter",
+  "backspace",
+  "copy",
+  "cut",
+  "paste",
+  "select_all"
+]

addedInput schema / properties / op / enum

Added value: +[
+  "tap",
+  "swipe",
+  "hotkey",
+  "type"
+]

changedInput schema / properties / slot / description

Previous value: -"Phone slot to control, given as the `slot` UUID from list-phones (its display name like \"slot12\" is not accepted). Must be cast/live."New value: +"Phone slot to control, given as the `slot` UUID from list-phones-tool (its display name like \"slot12\" is not accepted). The phone must show `video_live: true` there."

addedInput schema / properties / steps / maximum
```
Added value: +500
```
addedInput schema / properties / steps / minimum
```
Added value: +1
```

First observedSep 18, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond them: input is applied directly (not queued) and the call returns as soon as the phone acknowledges it, plus the live-video precondition. It does not discuss failure modes when the phone is not live, which holds it below a 5.

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?

Front-loaded with purpose and the sibling contrast, then a tight bulleted op list. Every sentence carries information and there is no redundancy with the schema.

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 mutation tool with no output schema, it covers the precondition, the divergence from the sibling tool, return timing, coordinate conventions, and each op's argument shape. An agent has everything needed to call 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 would be 3. The description earns more by explaining coordinate semantics beyond the schema (fractions of the screen, 0 = left/top, 1 = right/bottom) and by grouping parameters into ops (tap uses fx/fy, swipe uses fx1/fy1/fx2/fy2/steps), clarifying which params apply to which op.

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+resource ('Send one raw input to a farm phone') and immediately names the sibling it is not ('Unlike phone-command-tool, which queues a run'), so an agent can distinguish it without opening either schema. The op list further pins down exactly what 'input' means.

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?

It states an explicit prerequisite ('The phone must show video_live: true in list-phones-tool') and contrasts behavior with the phone-command-tool alternative (direct application vs queued run), which tells the agent which of the two to reach for. Nothing critical is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 0bull Phone Farm 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?