Skip to main content
Glama
Sign In
leeguooooo

iphone-use

by leeguooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

phone_capabilities

Read-only

Inspect supported UI operations and cached readiness before choosing an action. Read-only check names available modes and blocked reasons to guide next steps.

Instructions

Inspect supported UI operations and cached readiness before choosing an action. Unlike phone_status (device/setup/owner diagnostics), this names the backend's single-step, batch and perform vocabularies, observation support and accepted modes. Read-only: no device connection, wake or owner lease. supported is static; available is cached with blocked_by naming locked, released, reconnecting, human_handoff, owned_by_other or offline. ok:null is unknown, never proof of readiness. This describes UI control only, not app installation or other device management. If blocked, follow phone_status guidance instead of probing with actions.

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.6/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation: it discloses 'no device connection, wake or owner lease', that 'supported is static' while 'available is cached', the full blocked_by vocabulary, and critically warns 'ok:null is unknown, never proof of readiness'. This is exactly the kind of subtle behavioral context annotations cannot convey.

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?

Purpose is front-loaded and most sentences carry distinct, non-redundant facts. It is quite dense and packs several caveats into a short span, but nearly every clause (vocabularies, blocked_by values, ok:null warning) earns its place.

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, but the description explains the return semantics fully: supported vs available, blocked_by enumeration, and the ok:null ambiguity. Combined with the read-only annotation and complete parameter schema, an agent has everything needed to call and interpret it correctly.

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 'instance' parameter is fully documented in the schema, so the baseline of 3 applies. The description adds no further meaning to the instance parameter, but it doesn't need to since the schema is complete.

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+resource ('Inspect supported UI operations and cached readiness') and explicitly differentiates from the sibling phone_status ('Unlike phone_status (device/setup/owner diagnostics), this names the backend's single-step, batch and perform vocabularies'). An agent can distinguish the tool from its siblings without opening the 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 explicit when-to-use ('before choosing an action') and a named alternative with condition ('If blocked, follow phone_status guidance instead of probing with actions'). Also delimits scope ('This describes UI control only, not app installation or other device management'), routing installation work away.

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