Skip to main content
Glama

0bull Phone Farm

by net.0bull
OverviewDiscussionsAdmin

Phone Command Tool

phone-command-tool
Destructive

Send a device command to a farm phone. The phone must show video_live: true in list-phones-tool. Supported ops:

  • clipboard_set (text): set the phone clipboard

  • clipboard_get: read the phone clipboard back

  • open_url (url): open a URL / deep link

  • reboot: restart the phone

  • clear_photos: empty the camera roll

  • get_ip: report the phone's LAN IP

  • brightness (level): set screen brightness (0-1)

  • wifi / airplane / cellular / flashlight (on): toggle the named radio/flashlight Op-specific fields (text, url, level, on) are only sent when provided. Returns a run id. The run succeeds once the phone has run the command; for get_ip and clipboard_get its result.value holds the IP or clipboard text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
onNoDesired on/off state (for wifi, airplane, cellular, flashlight). Optional.
opYesCommand op: clipboard_set, clipboard_get, open_url, reboot, clear_photos, get_ip, brightness, wifi, airplane, cellular, flashlight.
urlNoURL or deep link to open (for open_url). Optional.
slotYesPhone slot to command, 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.
textNoText to set on the clipboard (for clipboard_set). Optional.
levelNoBrightness level 0-1 (for brightness). Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / level / maximum
      Added value: +1
    • addedInput schema / properties / level / minimum
      Added value: +0
    • addedInput schema / properties / op / enum
      Added value: +[
+  "clipboard_set",
+  "clipboard_get",
+  "open_url",
+  "reboot",
+  "clear_photos",
+  "get_ip",
+  "brightness",
+  "wifi",
+  "airplane",
+  "cellular",
+  "flashlight"
+]
    • changedInput schema / properties / slot / description
      Previous value: -"Phone slot to command, 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 command, 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."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds meaningful behavior beyond the destructiveHint=true annotation: async execution via a run id, success semantics ('run succeeds once the phone has run the command'), and which ops return a value. It does not spell out the destructive consequences of clear_photos or reboot or flag them as irreversible.

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?

The op list is tight and front-loaded as a scannable bullet block, with return-value note at the end. The header sentence plus 'op-specific fields' line adds slight redundancy but remains well under wasteful length.

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 command dispatcher with no output schema, the description covers the op set, when fields are sent, the async run-id model, and value-returning ops. That is everything an agent needs to invoke it correctly given the schema carries param details.

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 coverage is 100%, so parameters are already fully documented. The description re-lists ops and ties op-specific fields (text, url, level, on) to their ops and notes they are only sent when provided, which is mild added value but mostly repeats the schema.

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 and resource ('Send a device command to a farm phone'), enumerates all 11 supported ops, and cross-references list-phones-tool for slot resolution. An agent can distinguish it from siblings like phone-control-tool or phone-snapshot-tool without opening the schema.

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 gives a clear precondition ('The phone must show video_live: true in list-phones-tool') and how to resolve the slot UUID. However, it never explicitly states when to use phone-command-tool versus siblings like phone-control-tool, run-phone-agent-tool, or phone-ocr-tool.

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