Skip to main content
Glama
Sign In
leeguooooo

iphone-use

by leeguooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

phone_tap

Destructive

Taps a specific on-screen point on an iPhone using normalized x,y coordinates (0–1), for pixel-only targets that lack an accessible control.

Instructions

Tap a pixel target using normalized x,y from 0–1, with (0,0) at top-left. Prefer phone_tap_element for an accessible control; use phone_screenshot to locate a pixel-only target. Requires phone_status.drivable=true and current screen evidence: a tap may send, buy, delete or toggle whatever occupies that point, so authorize its actual effect first. observe defaults on and returns the settled screen change. Read outcome/retry_safe; if delivery is unknown, inspect the current state or receipt before considering another tap.

Input Schema

NameRequiredDescriptionDefault
xYesHorizontal position, normalized 0–1 (0 = left edge, 1 = right edge).
yYesVertical position, normalized 0–1 (0 = top edge, 1 = bottom edge).
observeNoOn by default: the result carries what the screen settled to — what changed since your last look (`delta`), or the whole tree the first time — so you rarely need `phone_elements` afterwards. The settled screen is also captured but NOT sent: `phone_screenshot` returns it at once if you need to see it. `false` skips both 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. Changed4 schema fields changedv0.22.4-glama.1
    • addedInput schema / properties / x / maximum
      Added value: +1
    • addedInput schema / properties / x / minimum
      Added value: +0
    • addedInput schema / properties / y / maximum
      Added value: +1
    • addedInput schema / properties / y / minimum
      Added value: +0
  3. First observedv0.21.0

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavioral context beyond annotations: destructive effects of tapping arbitrary coordinates, prerequisite status, default observe behavior, settled screen change, and the need to read outcome/retry_safe before repeating an uncertain tap. This aligns with and enriches the destructiveHint, non-idempotent, open-world annotations.

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?

Front-loads the core action and coordinate convention, then moves to sibling preference, prerequisites, safety warning, observe behavior, and retry guidance. Dense but every sentence earns its place with no filler.

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, open-world tap tool with no output schema, the description includes prerequisites, safety expectations, observe behavior, outcome/retry_safe semantics, and guidance on inspecting state before retrying. Nothing essential for correct invocation appears missing.

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 description coverage is 100%, so the schema already documents x, y, observe and instance thoroughly. The description reinforces the normalized coordinate system and observe default but does not add much parameter-level meaning beyond the schema, so baseline 3 is appropriate.

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 the specific action (tap a pixel target), the coordinate system (normalized x,y from 0–1 with top-left origin), and names phone_tap_element as the preferred sibling for accessible controls. It clearly distinguishes pixel-target tapping from element-based tapping.

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 says when to prefer phone_tap_element and when to use phone_screenshot to find a pixel-only target. It also states the prerequisite phone_status.drivable=true and warns that the agent must authorize the actual effect first because a tap can send, buy, delete or toggle.

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