Skip to main content
Glama
Sign In
leeguooooo

iphone-use

by leeguooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

phone_flow_run

Destructive

Run one installed or draft iPhone automation flow once, validate its step sequence, and report completed/applied counts plus the first failed step.

Instructions

Run one flow exactly once — an installed registry id, or a flow file path (*.json, e.g. a phone_flow_draft you are proving before publishing). A flow that declares outputs returns what it read as top-level outputs (e.g. today's steps); verify=true also checks their shape against the recorded fixture. A read_only/navigation flow that misses an element runs its other-language variant once (fallback_from says so): the daemon validates the whole sequence, holds one control lock, and stops at the first failed step. The happy path costs one tool call and zero screenshots. Requires phone_status drivable=true. Pass the flow's declared inputs; a flow declared risk=side_effect is refused unless confirm=true; a flow whose compat is broken or incompatible for the installed app version is refused unless force=true. The result reports completed/applied counts and the failed step; retry_safe=false means DO NOT replay — inspect phone_elements, repair the flow, do not guess. Unverified flows (verified=false in phone_flow_list) may need a checkpoint screenshot afterwards.

Input Schema

NameRequiredDescriptionDefault
idYesRegistry id such as `health/export-all` (see phone_flow_list), or the path of a flow file (`*.json`) — e.g. a draft saved by phone_flow_draft, to prove it on the phone before publishing.
forceNoRun even when compat is `broken` or `incompatible` for this phone.
inputsNoRuntime string inputs declared by the flow. Values are used for this run only and never persisted. Never pass passwords, codes, or private message content.
verifyNoCompare what the flow read (its `outputs`) against the recorded result shape; `verify.ok=false` names what drifted.
confirmNoRequired for flows declared `risk: side_effect`. Set true only after the user confirmed the target and inputs.
instanceNoInstalled local instance name, such as i13 or default. Omit to use the configured daemon. No fallback on failure.
write_fixtureNoWith verify: record this run's output shape as the fixture (types only). Only after checking the values are right.

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.8/5.0
Behavior5/5

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

Annotations declare a destructive, non-idempotent, open-world write, and the description goes well beyond them: one control lock is held, the daemon validates the whole sequence and stops at the first failed step, retry_safe=false forbids replay, and read_only flows auto-run their other-language variant with fallback_from reported. None of this contradicts the annotations and much of it cannot be inferred from them.

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 scope, and every sentence carries operational information (return shape, locking, fallback, refusal gates). It is dense as a single unbroken paragraph, which makes the retry_safe=false warning easy to miss, but there is little waste.

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?

There is no output schema, and the description compensates by explaining what comes back: top-level outputs, completed/applied counts, the failed step, verify.ok drift reporting, and fallback_from. For a 7-parameter destructive tool with nested inputs, an agent has everything needed to call it and to interpret the result.

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 per-field meaning is already documented and baseline is 3. The description adds cross-parameter semantics the schema does not: inputs are the flow's declared inputs used for one run only, confirm is gated on prior user confirmation, and force is tied to compat state — a modest but real value add.

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 verb and resource ('Run one flow exactly once') and immediately broadens the id semantics to registry id or *.json draft path, which separates it from phone_run_steps, phone_run_start and phone_flow_publish. It also names the sibling tools an agent would otherwise confuse with it (phone_flow_draft, phone_flow_list, phone_elements).

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?

Gives explicit preconditions ('Requires phone_status drivable=true'), refusal conditions (risk=side_effect needs confirm, broken/incompatible compat needs force), and an alternative action on failure ('inspect phone_elements, repair the flow, do not guess'). It also states that unverified flows may need a checkpoint screenshot, which routes the agent to the next tool.

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