Skip to main content
Glama
Sign In
ios-control-mcp

ios-control-mcp

by als0m3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

iphone_open_app

Launch an iPhone app by display name or bundle identifier to open it for the next automation step. Wait a couple of seconds after calling, since cold starts take a moment.

Instructions

Launch an app by display name or bundle identifier. Allow a couple of seconds before the next screenshot, as a cold start takes a moment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app": "<app>"
    },
    "name": "iphone_open_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes"Settings" or com.apple.Preferences.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full load. It usefully discloses cold-start latency and the need to pause before capturing a screenshot, which is real behavioral value. It leaves unresolved whether an already-running app is foregrounded or relaunched, and what happens when the app is not found.

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?

Two short sentences, front-loaded with the action, and the second sentence delivers non-obvious timing advice rather than filler. Nothing could be removed without losing information.

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 simple one-parameter action with no output schema, the definition covers the essentials: what it accepts and the practical timing consequence. The only notable omission is error behavior when the identifier doesn't match an installed app, plus a routing hint to iphone_list_apps.

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 parameter's description already gives the exact example ('Settings' or com.apple.Preferences). The description restates that both display names and bundle identifiers are accepted, adding only mild confirmation rather than new meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Launch an app') and notes both accepted identifier forms, which is enough to separate it from siblings like iphone_list_apps or iphone_tap. It doesn't explicitly name a sibling or contrast itself, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The sentence about allowing a couple of seconds before the next screenshot is practical workflow guidance that implies this tool should be followed by a screenshot or a wait. However, there is no explicit when-to-use/when-not-to-use framing and no pointer to iphone_list_apps as the way to discover valid bundle identifiers.

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