Skip to main content
Glama
Sign In
leeguooooo

iphone-use

by leeguooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

phone_screenshot

Read-only

Capture the current iPhone screen as a PNG when pixel-level detail matters, including optional element overlays and adjustable resolution for reading small text.

Instructions

Read one iPhone screen as an image/png content block when pixels matter; use phone_elements for text and semantic targets, or phone_screen to let the person watch a live MCP Apps panel. It reuses the captured settled frame after an observed action. max_side defaults to 1200; 0 requests full resolution. overlay=true draws interactive frames and their phone_elements indexes. Capture only for the current user task; private holds or offline devices can refuse it. Follow phone_status guidance instead of reconnecting for health checks. An image alone does not prove an action succeeded; check the target state or receipt.

Input Schema

NameRequiredDescriptionDefault
overlayNoDraw each interactive element's frame and its phone_elements index on the image, to match what you see with the rows you can tap.
instanceNoInstalled local instance name, such as i13 or default. Omit to use the configured daemon. No fallback on failure.
max_sideNoLongest side of the image in pixels. Default 1200, which reads fine and costs ~0.9k image tokens instead of ~1.5k at full resolution; ask for 0 (full resolution) only to read very small text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.27.34
    • addedInput schema / properties / max_side / minimum
      Added value: +0
  2. 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"
+}
  3. First observedv0.21.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint the description discloses non-obvious behavior: the frame is the settled capture reused after an observed action, overlay draws element frames with their phone_elements indexes, private holds or offline devices can refuse the call, and the ~0.9k vs ~1.5k image-token cost. The verification caveat is exactly the kind of behavioral warning annotations cannot express.

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 purpose and the sibling routing before any caveats, with no filler sentences. It runs long with several semicolon-joined constraints, but each carries distinct information an agent needs.

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 read-only capture tool with no output schema, the description still states the return shape (image/png content block), the token economics, the failure modes, and the limits of what the result proves. Nothing essential for calling it correctly is 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 explains overlay, instance, and max_side thoroughly. The description's restatement of the 1200 default and 0-for-full-resolution largely duplicates that, though tying overlay to phone_elements indexes adds a little cross-tool meaning. 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?

"Read one iPhone screen as an image/png content block when pixels matter" gives a specific verb, resource, return type, and the exact selection condition. It immediately distinguishes itself from phone_elements (text/semantic) and phone_screen (live panel), so an agent can route 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?

Explicit alternatives and their selection criteria are named: phone_elements for text/semantic targets, phone_screen for the human-visible live panel, phone_status for health checks instead of reconnecting. It also adds a scope constraint ("capture only for the current user task") and the caveat that an image alone does not prove success, with a redirect to check target state or receipt.

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