Skip to main content
Glama
Sign In
leeguooooo

iphone-use

by leeguooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

phone_status

Read-only

Read the iPhone's current status and control readiness without taking control, so you can confirm drivable, lock, setup, and recovery state before issuing device actions.

Instructions

Read the phone's status without taking control. owner names the session currently driving the phone (this session presents IPHONE_USE_OWNER, else mcp-); if it is someone else, do not drive the phone — control calls will be refused with phone_owned. The JSON preserves backend, target_configured, managed_runner, managed_runner_pending, recovery_owner, device_state, screen_state, runner, runner_actionable, locked, drivable, released, hint, next_step, recovery, setup_blocked_on, setup_phase, and setup_message. Gate actions on drivable=true. If target_configured=false and recovery_owner=unconfigured, phone_instances is only installed instances: inspect xcrun devicectl list devices and run iphone-use doctor on the daemon host; ask which phone if ambiguous, then IPU_RUNNER_UDID= iphone-use setup for the confirmed target only when the task authorizes it. Preserve --instance for named instances. lock_readiness says whether the phone locks on its own when idle (passcode_protected, auto_lock_secs, keep_awake, verdict, hint): will_lock_needs_person means a person must unlock it after a pause; tell the owner the hint instead of retrying. For trust, distinguish Trust This Computer pairing from developer-certificate approval under iPhone Settings > General > VPN & Device Management; use setup_message evidence. A separate passcode/automation prompt may appear later. needs_passcode_on_phone records a possible authorization requirement, not a confirmed visible prompt. Relay next_step; never request a passcode, pause screenshots/elements during sensitive input, and check status after the person finishes. Do not loop reconnect. keep_runner_alive (non-null) means idle release keeps the runner up because its next start would need a person. For status/health checks, report the state and stop. Idle release is intentional: reconnect (phone_reconnect, once) only when a current user-requested task needs the phone, recovery_owner=daemon, and no blocker or reconnect is in progress; then poll until drivable=true.

Input Schema

NameRequiredDescriptionDefault
instanceNoInstalled local instance name, such as i13 or default. Omit to use the configured daemon. No fallback on failure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.27.3
    • addedInput schema / properties / instance
      Added value: +{
+  "description": "Installed local instance name, such as i13 or default. Omit to use the configured daemon. No fallback on failure.",
+  "type": "string"
+}
  2. First observedv0.21.0

TDQS

A4.7/5.0
Behavior5/5

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

With readOnlyHint already covering safety, the description goes far beyond: it discloses the owner/refusal semantics (phone_owned), the full field list preserved in the JSON, the keep_runner_alive meaning, that idle release is intentional, and passcode/trust subtleties. This is substantive behavioral context annotations cannot carry.

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

Conciseness3/5

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

Purpose is front-loaded, but the body is a dense wall of imperative sentences mixing routing, recovery, trust, and passcode guidance. Much is relevant, yet it's hard to scan and some prose could be compressed without losing meaning.

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 read-only status tool with no output schema, the description enumerates the returned fields and explains gating, recovery, setup, and reconnect decisions. An agent has enough to interpret results and act 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 real nuance beyond the schema: 'Preserve --instance for named instances' and the no-fallback caveat, giving the agent usage guidance the schema doesn't.

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?

Opens with a specific verb and resource: 'Read the phone's status without taking control.' The 'without taking control' clause explicitly distinguishes it from the many driving/control siblings (phone_tap, phone_type, etc.).

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?

Explicit when-to-use ('For status/health checks, report the state and stop') and when-not (reconnect only under a named set of conditions, do not loop reconnect). It also names the alternative sibling phone_reconnect and the exact preconditions for calling it.

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

Deploy Server

Other Tools