Skip to main content
Glama

iphone_list_apps

Read-onlyIdempotent

Lists installed iPhone apps with names and bundle IDs so you can find the exact identifier needed to launch or close an app when its name is ambiguous or unknown.

Instructions

List the apps installed on the iPhone as 'Name — bundle ID' lines, sorted by name.

Use it to find the exact bundle ID or name for iphone_launch_app / iphone_close_app when a name is
ambiguous or not found. Needs the cable or Wi-Fi sync; otherwise it lists the built-in Apple apps it
knows. Reads only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "iphone_list_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoOnly list apps whose name or bundle ID contains this text (case-insensitive).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / filter / description
      Added value: +"Only list apps whose name or bundle ID contains this text (case-insensitive)."
  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?

Annotations already declare readOnly/idempotent/non-destructive, so 'Reads only' is a minor restatement. The genuinely additive detail is the degraded-mode behavior: without a cable or Wi-Fi sync it only lists known built-in Apple apps, which an agent would otherwise misread as a complete inventory.

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 tight paragraphs: the capability and output format first, then the usage/limitation note. No filler sentences and nothing buried.

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, read-only listing tool with an output schema, everything an agent needs is present: what it returns, when to reach for it, and the connectivity caveat that changes what comes back.

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 100% and the single 'filter' parameter is fully documented (case-insensitive substring on name or bundle ID) in the schema. The description adds nothing about filtering, so the 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 (list the apps installed on the iPhone) plus the exact output shape ('Name — bundle ID' lines, sorted by name). This is instantly distinguishable from siblings like iphone_status or iphone_ui_tree.

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?

Explicitly names the downstream alternatives (iphone_launch_app / iphone_close_app) and the condition that should trigger this tool: when a name is ambiguous or not found. That is real routing guidance rather than vague context.

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