run-sequence-android-mcp

Overview Schema Source Related Servers Discussions Admin

Install App

android_install_app

Installs an APK file on an Android device or emulator, letting you target a specific device and optionally grant runtime permissions for testing.

Instructions

Install an APK file on the device.

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

Input Schema

Name	Required	Description
`device`	No	Device id (serial or host:port). Optional -- when omitted, uses ANDROID_MCP_DEVICE env or auto-selects the connected device (physical devices preferred over emulators).
`apkPath`	Yes	Absolute path to the .apk file on this computer
`grantPermissions`	No	Grant all runtime permissions at install time (useful for testing)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

C2.7/5.0

Behavior2/5

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

The description only states 'Install an APK file' without disclosing behavioral traits. It does not mention whether the app is launched after installation, whether existing versions are overwritten, or what happens on failure. Since annotations are empty, the description must carry the full burden, and it fails to do so.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but at the expense of important details. It is underspecified rather than efficiently dense. Every sentence should earn its place, and this one only states the obvious.

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

Completeness2/5

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

Given no output schema and no annotations, the description should provide more context about what happens after install (e.g., return value, error codes). It also lacks any mention of device selection behavior or permission handling, leaving an agent with insufficient information.

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 the input schema already describes all parameters (device, apkPath, grantPermissions). The description adds no extra meaning beyond the schema. Baseline of 3 is appropriate because the schema does the heavy lifting, leaving little room for the description to add value.

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 clearly states the tool installs an APK file on a device. It uses a specific verb ('Install') and specifies the resource ('APK file'). While it could be more precise (e.g., 'on the connected Android device'), it is unambiguous and distinguishes from sibling tools like 'android_launch_app' or 'android_uninstall_app'.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention that the device must be connected, that the APK must exist at the specified path, or that permissions might be needed. There is no mention of prerequisites or typical use cases.

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