Skip to main content
Glama
Sign In
android-mcp

android-mcp

by mii-shell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

clear_app_data

Deletes all data for a specified Android app package and stops it, resetting the app to a fresh-install state.

Instructions

Delete all data of an app (like a fresh install). Also stops it.

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

Input Schema

NameRequiredDescriptionDefault
serialNoadb serial; optional when exactly one device is connected
packageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that all app data is deleted and that the app is stopped, but it omits whether the deletion is irreversible, what permissions or confirmations are required, and how failures are handled.

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 compact sentence delivers the destructive action, the fresh-install analogy, and the stop side effect with no wasted text. It is front-loaded and appropriately sized.

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 destructive operation with no annotations and no output schema, the description covers the core action and side effect but leaves important operational gaps: reversibility, error behavior, and confirmation requirements are unstated.

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 50%: serial is documented in the schema, while package has no schema description. The tool description maps package to the target app, but does not add package format details or explain device-selection behavior beyond what the schema already implies.

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 and resource: deleting all app data, compared to a fresh install, and also stopping the app. It is clear enough to distinguish from stop_app, but it does not explicitly name or contrast sibling tools.

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 phrase 'like a fresh install' implies the reset use case, but there is no explicit guidance on when to use this instead of stop_app or launch_app, and no exclusions or prerequisites are stated.

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