Skip to main content
Glama
Sign In
Android Studio MCP

Android Studio MCP

by crimSun-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Launch app

app_launch

Launch an Android app's launcher or specified activity on a device and report launch time, optionally force-stopping first for a cold start.

Instructions

Start an app's launcher activity (or a given activity) and report launch time.

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": "<package>"
    },
    "name": "app_launch"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialNoDevice serial from devices_list. Optional when exactly one device is online.
packageYesApplication package / applicationId
activityNoActivity class, e.g. .MainActivity or com.x.MainActivity. Defaults to the launcher activity.
stopFirstNoForce-stop the app before launching (cold start)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, yet it only states that a launch happens and launch time is reported. It doesn't disclose the default force-stop (cold start) side effect exposed by stopFirst, what 'launch time' means, what happens if the package isn't installed, or whether an already-running instance is killed.

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 tight sentence that front-loads the core action and the launcher-activity default. There is no wasted text, though the compression leaves behavioral gaps rather than filling them.

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 four-parameter mutation tool with no annotations and no output schema, the description is minimally viable. It omits device targeting behavior, cold-start semantics, and failure modes, so an agent could call it but would be guessing at side effects.

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 100%, so all four parameters, including serial selection and the stopFirst cold-start default, are documented in the schema. The description only echoes the activity-vs-launcher distinction already covered there, so it adds nothing beyond the structured fields.

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 (start) and resource (an app's launcher activity, or a named activity) and notes it reports launch time. It doesn't distinguish itself from nearby siblings like run_app or app_stop, so an agent must infer that this is low-level ADB-style launching rather than a Gradle/IDE run.

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?

There is no guidance on when to use this instead of run_app, app_stop, or input/emulator tools, nor any preconditions such as the app being installed or a device being selected. The agent is left to infer usage entirely.

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

Deploy Server

Other Tools