@wilsonbeam/openclaw-adb-mcp

Overview Schema Source Related Servers Discussions Admin

adb_install_app

Install an APK file on an Android device using ADB, with options to reinstall existing apps and grant runtime permissions automatically.

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": "adb_install_app"
  }
}

Input Schema

Name	Required	Description
`apkPath`	Yes	Path to the APK file
`deviceId`	No	Target device ID (optional)
`reinstall`	No	Reinstall the app if it exists
`grantPermissions`	No	Grant all runtime permissions

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 6, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It only states 'Install an APK file on the device' without mentioning side effects (e.g., overwriting existing app, granting permissions), failure modes, or device selection.

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?

A single sentence that directly states the tool's purpose. No wasted words or redundancy.

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?

For a mutation tool with no annotations and no output schema, the one-line description is insufficient. It omits behavior around optional parameters (deviceId, reinstall, grantPermissions) and prerequisites like device connectivity, even though the schema defines them.

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?

The schema provides descriptions for all four parameters (apkPath, deviceId, reinstall, grantPermissions) at 100% coverage. The description adds no extra semantics beyond the schema, hence the baseline score of 3.

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?

The description uses the specific verb 'install' with resource 'APK file' and target 'device', clearly distinguishing it from siblings like adb_uninstall_app. It is concise and unambiguous.

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 gives no guidance on when to use this tool versus alternatives such as adb_uninstall_app or adb_list_packages. There are no prerequisites, exclusions, or alternative tools mentioned.

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