Skip to main content
Glama

iphone_launch_app

Idempotent

Launch an iPhone app by name or bundle ID, or bring a running app to the front while preserving its state.

Instructions

Open an app, or bring it to the front if it is already running (its state is kept).

Faster and more reliable than finding and tapping its icon on the home screen. To start an app fresh,
call iphone_close_app first. To open a specific page or link inside an app, use iphone_open_url.

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_launch_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesApp name as shown on the home screen (e.g. 'Settings', 'Einstellungen', 'Safari') or bundle ID (e.g. 'com.apple.Preferences').

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • addedInput schema / properties / app / description
      Added value: +"App name as shown on the home screen (e.g. 'Settings', 'Einstellungen', 'Safari') or bundle ID (e.g. 'com.apple.Preferences')."
    • addedInput schema / properties / app / minLength
      Added value: +1
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true; the description adds real meaning by explaining what idempotency looks like here — an already-running app is foregrounded with its state preserved. It does not cover failure behavior, such as what happens if the app name is unknown or not installed.

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?

Three short sentences, front-loaded with what the tool does, then when to prefer it, then the two sibling alternatives. No filler or repetition.

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 one-parameter tool with full schema coverage, rich annotations and an output schema, the description supplies everything an agent needs: core behavior, the running-app case, and explicit sibling routing. Return values need no explanation given the output schema exists.

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?

The single parameter has 100% schema description coverage, including localized-name and bundle-ID examples, so the schema carries the semantics. The description never mentions the `app` argument or the accepted formats, adding nothing beyond it; baseline 3 applies.

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 ("Open an app") plus the precise edge-case behavior ("bring it to the front if it is already running"). It explicitly distinguishes itself from iphone_close_app and iphone_open_url, so an agent can separate the three 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?

Gives an explicit routing rule for the fresh-start case ("call iphone_close_app first") and for deep links ("use iphone_open_url"). It also justifies choosing this over UI-level interaction by noting it is faster and more reliable than tapping the home-screen icon.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.