@wilsonbeam/openclaw-adb-mcp

by wilsonbeam

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

adb_uninstall_app

Uninstall an Android app from a connected device using its package name. Optionally preserve app data and cache.

Instructions

Uninstall an app from 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": {
      "packageName": "<packageName>"
    },
    "name": "adb_uninstall_app"
  }
}

Input Schema

Name	Required	Description
`deviceId`	No	Target device ID (optional)
`keepData`	No	Keep app data and cache
`packageName`	Yes	Package name of the app (e.g., com.example.app)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 6, 2026

TDQS

A3.5/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 destructive action but does not mention side effects like permanent removal of app data, limitations on system apps, or permission requirements. The description adds no value beyond the tool name itself.

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 a single, front-loaded sentence with zero wasted words. Every word contributes to meaning, making it highly concise and clearly structured.

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?

The tool is simple and the schema is fully descriptive, so the minimal description covers the basic purpose. However, it lacks contextual details like data-handling behavior and relationship to sibling tools, making it only minimally complete.

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 descriptions cover all three parameters (packageName, deviceId, keepData) with 100% coverage. The description itself adds no parameter-level detail, so a baseline score of 3 is appropriate.

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 a specific verb 'Uninstall' and a clear resource 'app from the device', which distinguishes it from sibling tools like adb_install_app and adb_clear_data. It unambiguously states the tool's function.

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

Usage Guidelines3/5

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

The description implies when to use the tool (when an app needs to be removed) but provides no explicit comparison to alternatives such as adb_force_stop or adb_clear_data. It lacks clear context about when not to use it, but the core usage is understandable.

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