Skip to main content
Glama

ios_launch_app

Launch iOS apps by alias, Bundle ID, or URL Scheme deep link so MCP clients can open target apps without a tethered Mac.

Instructions

Launch an app by alias, Bundle ID, or URL Scheme DeepLink.

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_target": "<app_target>"
    },
    "name": "ios_launch_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_targetYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses almost nothing beyond the verb. It does not say that launching mutates device state by displacing the current foreground app, nor how failures are reported when the alias or Bundle ID resolves to nothing.

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?

A single front-loaded sentence with no filler; the accepted-format list is placed where it is most useful. It is terse to the point of leaving prerequisites and failure behavior unstated, but nothing in the text is wasted.

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

Completeness3/5

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

With an output schema present, return values need no explanation, and one parameter keeps the surface small. Still, for a state-changing device action with zero annotation coverage, the description omits prerequisites and error conditions that an agent would need before calling it reliably.

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 description coverage is 0% for the single required parameter app_target, so the description must compensate, and it partially does by naming the three accepted identifier forms. However, it gives no format examples or precedence rules for when a value could match more than one form (for example, an alias that is also a Bundle ID).

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 pairs a specific verb ("Launch") with a specific resource ("app") and enumerates the three accepted identifier types (alias, Bundle ID, URL Scheme DeepLink). This clearly distinguishes it from the UI-interaction siblings such as ios_tap or ios_input_text, though it makes no explicit reference to any sibling for contrast.

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 three accepted target formats imply when the tool applies (bringing an app forward by any of several identifiers), but there is no explicit when-to-use/when-not-to-use guidance, no prerequisites such as the target app being installed or the device session being active, and no stated alternatives.

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