Skip to main content
Glama
Sign In
devilge

devilge

by Yercko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Wipe app data (DESTRUCTIVE)

devilge_clear_app_data
Destructive

Clears all app data including caches, databases, and preferences to reset an app to fresh install state on next launch. Intended for development emulators only.

Instructions

Runs pm clear <pkg> — wipes all app data including caches, databases, SharedPreferences, tokens. The app behaves like a fresh install on next launch. DESTRUCTIVE. Recommended only on dev emulators or wiped test devices, never on personal devices with logged-in apps.

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

Input Schema

NameRequiredDescriptionDefault
serialNoDevice serial. Defaults to DEVILGE_DEFAULT_DEVICE_SERIAL or the only attached device.
packageNameYesApp applicationId whose data will be wiped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A4.5/5.0
Behavior5/5

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

While annotations already indicate `destructiveHint=true`, the description adds specific behavioral details: the exact command (`pm clear <pkg>`), what data is wiped, and the result (app behaves like fresh install). This significantly enhances the agent's understanding beyond annotations.

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 extremely concise: two sentences plus a bold warning. Every sentence adds value, and the key command and warning are front-loaded.

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

Completeness5/5

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

For a simple tool with 2 parameters and no output schema, the description covers purpose, behavior, and safety adequately. No gaps remain.

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 100%, so the description adds no additional parameter meaning beyond what the schema provides. 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 clearly states the tool wipes all app data via `pm clear`, specifying exactly what is removed (caches, databases, SharedPreferences, tokens) and the effect (fresh install). This distinguishes it from sibling tools like `devilge_launch_app` or `devilge_force_stop_app`.

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

Usage Guidelines4/5

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

The description explicitly recommends using it only on dev emulators or wiped test devices and warns against personal devices. However, it does not mention alternative tools for non-destructive data operations, so a slight deduction.

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