Skip to main content
Glama
Sign In
leeguooooo

iphone-use

by leeguooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

phone_hold

Idempotent

Pause a user-requested iPhone task for a set time so a person can enter a PIN or approval code without the idle watchdog releasing the device. Clear the hold when done.

Instructions

Keep the phone for a bounded human-in-the-loop pause inside the current user-requested task (the operator types a PIN, approves a prompt, fetches a code): the idle watchdog will not release it for secs seconds (0 clears the hold; max 14400). When the person signs in (passcode, Face ID, a code), pass private=true: the screen is not read or streamed until you clear the hold; pass private=true again when extending it, since a hold without it lifts the privacy. Not for initialization, health checks, or keeping the phone ready; clear it when the step is done. Fails with device_release_in_progress if the daemon is already releasing, and with phone_owned if another session holds the phone lease.

Input Schema

NameRequiredDescriptionDefault
secsYesSeconds to keep the phone (0 clears the hold; at most 14400).
privateNoThe person is signing in (passcode, Face ID, a code): nothing reads the screen until the hold ends or is cleared — screenshots, elements and live views are refused with `screen_private`.
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.34
    • addedInput schema / properties / secs / 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.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses watchdog semantics, the 0-clears and max-14400 bounds, the private-mode consequence (screen not read or streamed, and that extending without private lifts privacy), and two named failure modes (device_release_in_progress, phone_owned). Annotations only cover the safety profile (readOnlyHint=false, idempotentHint=true), so this added context is substantial.

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-loads the core action and bounds, then packs guidance, privacy rules, and error conditions in that order. It is dense but every clause carries operational meaning; the single long paragraph and parenthetical asides make it slightly harder to scan than a bulleted form would.

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 mutating, timer-based lease tool with no output schema, the description covers purpose, bounds, privacy implications, cleanup, and failure modes. An agent has everything needed to invoke it correctly and avoid the common misuse of leaving a stale hold.

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 earns more by tying `private` to a real situation ('when the person signs in') and warning that it must be re-passed on extension or the privacy lapses — a non-obvious coupling the schema only partly conveys. It does not clarify the `instance` fallback behavior, which the schema already documents.

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: 'Keep the phone for a bounded human-in-the-loop pause inside the current user-requested task,' and gives concrete examples of what the operator does (types a PIN, approves a prompt, fetches a code). It also carves out the scope against sibling behaviors ('Not for initialization, health checks, or keeping the phone ready'), so an agent can distinguish it from phone_status or phone_capabilities.

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 when-to-use (a human step in the current task), explicit when-not ('Not for initialization, health checks, or keeping the phone ready'), and an explicit termination rule ('clear it when the step is done'). The guidance is actionable without opening any schema.

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