Skip to main content
Glama
Sign In
leeguooooo

iphone-use

by leeguooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

phone_flow_update

Idempotent

Sync the official iphone-use flow registry into the local store with checksum-verified validation, keeping locally added flows intact. Run it when the flow list is empty or to pick up new flows.

Instructions

Mirror the official iphone-use flow registry (github.com/leeguooooo/iphone-use-flows) into the local store. Every file is checksum-verified and strictly validated before it is written; locally added flows are kept. Call once when phone_flow_list reports an empty store, or to pick up new flows. Network only; the phone is not touched.

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.4/5.0
Behavior4/5

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

Annotations already declare idempotent, non-destructive, open-world behavior; the description adds the concrete reason ('locally added flows are kept') plus checksum verification and strict pre-write validation, so an agent knows local edits survive. It does not say what happens to partially failed syncs or whether network errors are reported as a list.

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?

Three sentences with zero padding: what it does, its safety properties, then the call condition. The scope statement is front-loaded and the guidance is last, which is the natural reading order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the essentials of a network-fetching, store-mutating tool with no output schema: what is written, how it is validated, what is preserved, and that the phone itself is untouched. Missing only failure-mode detail (what an agent sees on a partial or checksum-failed sync).

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% and the single optional 'instance' parameter is documented there with its fallback behavior, so the description adds no parameter meaning. Baseline 3 applies when the schema carries the full burden.

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: mirror the official iphone-use flow registry into the local store. It is clearly distinguishable from phone_flow_list (read), phone_flow_draft (authoring) and phone_flow_publish (pushing out) named among the siblings.

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 an explicit trigger ('Call once when phone_flow_list reports an empty store, or to pick up new flows'), tying usage to a named sibling's output. It also bounds the call ('call once'), which prevents a polling loop.

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