replicant-mcp

adb-app

Destructive

Manage Android apps on emulators or devices by installing, uninstalling, launching, stopping, clearing data, or listing apps.

Instructions

Manage applications.

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": {
      "operation": "<operation>"
    },
    "name": "adb-app"
  }
}

Input Schema

Name	Required	Description
`operation`	Yes
`apkPath`	No	APK path
`packageName`	No
`limit`	No	Default: 20, max: 100
`filter`	No	Filter by name (case-insensitive)
`offset`	No	Pagination offset

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.6.7May 13, 2026
- addedInput schema / properties / limit / maximum
```
Added value: +100
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```

Changed5 schema fields changedv1.0.1Apr 2, 2026

changedInput schema / properties / apkPath / description

Previous value: -"Path to APK file (for install)"New value: +"APK path"

addedInput schema / properties / filter

Added value: +{
+  "description": "Filter by name (case-insensitive)",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Default: 20, max: 100",
+  "type": "number"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Pagination offset",
+  "type": "number"
+}

removedInput schema / properties / packageName / description
```
Removed value: -"Package name (for other operations)"
```

First observedv1.0.0Jan 21, 2026

TDQS

C2.2/5.0

Behavior2/5

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

Annotations indicate destructiveHint=true (mutates state) and readOnlyHint=false, but the description adds no behavioral context beyond what annotations already convey. It does not explain side effects, permissions needed, or that operations like 'clear-data' are destructive.

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?

At three words, the description is under-specified, not concise. For a tool with 6 parameters and multiple operations, it should provide structured detail without wasting words. Current form fails to inform.

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 the tool's complexity (6 parameters, no output schema, multiple operations), the description is inadequate. It does not explain return values, pagination behavior, or how operations like 'list' work. The agent has to infer everything from parameter names and enum values.

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 description coverage is 67%, with some parameters (apkPath, limit, filter) having descriptions. The description 'Manage applications' does not add meaning beyond the schema. However, the moderate coverage means the schema partially compensates, so a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Manage applications' is vague and does not specify the supported operations (install, uninstall, launch, etc.). The input schema lists operations but the description fails to enumerate them, making it unclear what this tool specifically does compared to siblings.

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 siblings like adb-device or adb-logcat. The description offers no context for selecting this tool for app management tasks.

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

Deploy Server