Skip to main content
Glama

phone_open_app

Launch an installed Android app by name or package; optionally open its Play Store search if not installed.

Instructions

Open (launch) an installed app by its name ("WhatsApp") or package ("com.whatsapp"). With store=true, an app that is not installed is shown in the Play Store instead (nothing is installed automatically).

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": {
      "name": "<name>"
    },
    "name": "phone_open_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
afterNo
storeNoif not installed, open its Play Store search
settleNomax ms to wait for it to finish opening (default 5000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the valuable non-obvious behavior that store=true only surfaces the Play Store listing and never installs anything, but it omits failure behavior when the app is missing and store is false, whether the launch blocks, and whether the app is brought to the foreground.

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 sentences with the primary action and accepted input formats front-loaded, followed by the single most important caveat. No filler or restatement of the tool name.

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?

For a 4-parameter action tool with no annotations and no output schema, the definition covers the happy path and the store fallback well but leaves the `after` parameter and the not-found/error path undocumented. An agent could call it correctly in the common case but would be guessing on those two points.

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 only 50%, and the description usefully compensates for `name` by showing both a display-name and a package-name example. However, the `after` parameter is left entirely undefined in both schema and description, and `store`/`settle` are already documented in the schema, so half the surface remains unexplained.

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 (launch) an installed app') and immediately gives both accepted identifier forms with concrete examples ("WhatsApp" / "com.whatsapp"). This is clearly distinguishable from siblings like phone_open_link (URLs) and phone_stop_app (terminating).

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?

The scope is clear: open an already-installed app, with the store=true variant as the explicit fallback path when it is not installed. It also sets a boundary by stating nothing is installed automatically, though it never names a sibling alternative or says what to do if the app is absent and store is false.

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