Skip to main content
Glama
Sign In
leeguooooo

iphone-use

by leeguooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

phone_install_app

Destructive

Install an .ipa or .app on a connected iPhone or simulator from a Mac path or HTTPS URL. Use fresh mode to remove existing app data for a clean install.

Instructions

Install an app build on the phone: path of an .ipa or .app on the Mac running the daemon, or an https url of an .ipa (up to 2 GB). fresh=true uninstalls the app first, deleting its data. Apps the operator blocked are refused. Answers with the installed bundle id; it can take minutes. Install only what the user asked for.

Input Schema

NameRequiredDescriptionDefault
urlNoAn https URL of an `.ipa` (at most 2 GB); the daemon downloads it.
pathNoAbsolute path of an `.ipa` or `.app` on the Mac running the daemon.
freshNoUninstall the app first (its data goes with it), for a clean start.
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 annotations: it discloses that fresh=true uninstalls first and destroys app data, that blocked apps are refused, that the call can take minutes, and what is returned (the installed bundle id). That is exactly the extra context an agent needs for a destructive, slow, non-idempotent operation.

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?

One dense but front-loaded paragraph: the core action and accepted sources come first, then behavior, then the safety caveat. No filler sentences and nothing redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-output-schema, four-parameter mutation tool this covers duration, failure mode (blocked apps), data loss, and return value. It omits any mention of the `instance` selector, which is the only remaining gap.

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 already 100%, but the description adds meaning by presenting path and url as mutually exclusive source choices and by spelling out the side effect of fresh (data deletion). The `instance` parameter is left to the schema, keeping it just short of a 5.

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 ("Install an app build on the phone") and enumerates the two source forms (local path vs https url), so an agent immediately understands the operation and its inputs. No sibling tool overlaps with installing apps, and the description makes that distinction obvious 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a real usage constraint ("Install only what the user asked for") plus the conditional rule for fresh=true and the refusal of operator-blocked apps. It stops short of naming alternatives or when-not-to-install scenarios more broadly, but the context needed to pick and use this tool is clear.

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