Skip to main content
Glama
Sign In
leeguooooo

iphone-use

by leeguooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

phone_flow_list

Read-only

Find installed per-app automation flows so a matching recorded flow can replay a task without model decisions or screenshots; filter by category, app, or hardware verification.

Instructions

Find installed deterministic per-app flows before exploring a task: a matching phone_flow_run can replay it without model decisions or screenshots. Filters category, app and verified combine; app is a registry app directory or bundle id, not a display-name search. Compact rows report id, description, inputs, risk and compatibility with this phone's app version; detail=true returns full JSON. verified means a recorded hardware run, not a guarantee for every current version. Use phone_flow_info to inspect effects before running. An empty store needs phone_flow_update once; a filter with no matches is not proof that the whole store is empty.

Input Schema

NameRequiredDescriptionDefault
appNoOnly flows for this app directory (e.g. `health`) or bundle id.
detailNoReturn every field of every entry (verified_on, app versions, step counts) as JSON text instead of one compact row per flow.
categoryNoOnly flows in this registry category (e.g. `health`, `system`, `finance`, `im`).
instanceNoInstalled local instance name, such as i13 or default. Omit to use the configured daemon. No fallback on failure.
verifiedNoOnly flows with at least one recorded hardware verification.

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?

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses that filters AND-combine, that app takes a registry directory or bundle id and is explicitly NOT a display-name search, what the compact row contains, what detail=true changes, and the important caveat that 'verified' means a recorded hardware run rather than a per-version guarantee. That is exactly the kind of semantic and trust caveat structured fields 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.

Conciseness4/5

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

Front-loaded with purpose then alternative then caveats, and every clause is substantive rather than filler. It is dense to the point of being a run-on in places, but trimming any sentence would lose real information.

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?

No output schema exists, and the description compensates by describing the compact row fields (id, description, inputs, risk, compatibility) and what detail=true returns. Combined with the empty-store and verification caveats, an agent has enough to call this correctly and 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 the baseline is 3; the description earns a bump by adding filter-combination semantics and the app-parameter disambiguation ('registry app directory or bundle id, not a display-name search') that the schema text does not state. It does not add much on `instance` or `detail` beyond what the schema already documents.

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 ('Find installed') and resource ('deterministic per-app flows') with scope ('before exploring a task') and immediately distinguishes itself from phone_flow_run by noting a match can replay without model decisions. An agent can tell this apart from phone_flow_info, phone_flow_run and phone_flow_update without opening any schema.

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?

Explicitly positions the tool in a workflow ('before exploring a task'), names the alternative for deeper inspection ('Use phone_flow_info to inspect effects before running'), and gives the remediation path for the empty case ('An empty store needs phone_flow_update once'). It even forecloses a false conclusion ('a filter with no matches is not proof that the whole store is empty').

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