Skip to main content
Glama
Sign In
leeguooooo

iphone-use

by leeguooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

phone_tap_label

Destructive

Taps an iPhone UI element by its exact visible label. Reads a fresh element snapshot, requires a single match, then performs the tap; zero or multiple matches return an error without acting.

Instructions

Tap an iPhone UI element by an EXACT visible label (requires drivable=true in phone_status). Reads a fresh phone_elements snapshot, requires exactly one match, then performs a snapshot-bound tap. Zero or multiple matches return an error and send NO action. For duplicate labels, choose by identifier/kind/state from phone_elements and call phone_tap_element with that response's snapshot.

Input Schema

NameRequiredDescriptionDefault
labelYesThe element's visible accessibility label, exactly as shown by `phone_elements` (e.g. "新备忘录", "Connect").
observeNoDefault true: return what the screen settled to (as on phone_tap). `false` for the fastest bare action.
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.9/5.0
Behavior5/5

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

Annotations only declare that this is a destructive, non-idempotent open-world write. The description adds materially: zero or multiple matches send NO action, the tap is bound to a specific phone_elements snapshot (staleness risk), and a fresh snapshot is read before acting. That is exactly the safety context an agent needs before a destructive tap.

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, front-loaded with the action, then the failure contract, then the fallback path. Every clause carries either a constraint or a routing instruction; nothing is padding.

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 destructive, non-idempotent tap with no output schema, the description covers the precondition (drivable status), the failure behavior, the snapshot-binding semantics, and the observe=true return notion. An agent has everything needed to call it 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 still adds the crucial constraint that 'label' must resolve to exactly one match, otherwise the call errors. The instance/observe parameters are left entirely to the schema, which is acceptable given full coverage.

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 ('Tap an iPhone UI element by an EXACT visible label') and implicitly separates itself from phone_tap (coordinate-based) and phone_tap_element (identifier-based). An agent can pick the right sibling 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?

Gives an explicit prerequisite ('requires drivable=true in phone_status'), the exact selection rule (one match only), and a named alternative for the ambiguous case: use phone_tap_element with the snapshot from phone_elements when labels duplicate. That is when-to-use, when-not, and where-to-go instead, all in one place.

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