Ultimate Android MCP

Overview Schema Source Related Servers Discussions Admin

launch_app

Starts an Android app on a connected device using its package name. Specify the package_name to launch the app directly via ADB.

Instructions

Launches the app with the specified package name on the connected Android device. Requires the package_name parameter, which is the package name of the app to be launched.

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

Input Schema

Name	Required	Description	Default
`package_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 15, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the primary action, but does not explain what happens if the app is already running, whether the app is brought to the foreground, what error behavior occurs for a missing package, or any side effects.

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?

The description is two sentences with no filler. It front-loads the action and device context, and the redundant 'requires package_name' sentence is short and harmless.

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 one-parameter tool with a simple action, the description provides the minimum needed to attempt a call. However, without annotations, output schema, or guidance on expected return/failure states, it is only minimally viable rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It adds only a near-tautological explanation that package_name is the package name of the app to be launched, without format, examples, constraints, or guidance on how to find the package name.

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 ('Launches the app'), a specific resource ('the app with the specified package name'), and the device context ('on the connected Android device'). It is clear, though it does not explicitly differentiate itself from related sibling tools like install_apk or is_installed.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, no exclusions, and no conditions such as 'use this when the app is already installed.' It only restates that the package_name parameter is required.

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