Skip to main content
Glama

clear_app_data

Clear app data for a specific Android application on a connected device by providing its package name.

Instructions

Clear app data for a specific app on the connected Android device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYes

Implementation Reference

  • The handler function for the 'clear_app_data' tool. It uses ADB to clear the app data for the specified package name. The @mcp.tool() decorator registers this function as an MCP tool.
    @mcp.tool()
    def clear_app_data(package_name: str) -> str:
        """Clear app data for a specific app on the connected Android device"""
        result = subprocess.run(
            ["adb", "shell", "pm", "clear", package_name], capture_output=True, text=True
        )
        if result.returncode != 0:
            raise RuntimeError(f"Error clearing app data for '{package_name}': {result.stderr}")
        return f"App data for '{package_name}' has been cleared."
  • The @mcp.tool() decorator registers the clear_app_data function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Clear app data') but doesn't explain what this entails—e.g., whether it deletes user settings, cache, or all stored data, or if it's reversible. This leaves critical behavioral traits unspecified for a potentially destructive operation.

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, direct sentence with no wasted words, making it easy to parse quickly. It front-loads the core action and target efficiently, achieving optimal conciseness for its purpose.

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 (a potentially destructive operation on an Android device), lack of annotations, no output schema, and 0% schema coverage, the description is insufficient. It doesn't cover behavioral details, parameter semantics, or expected outcomes, leaving significant gaps for safe and effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the undocumented parameter. It mentions 'for a specific app' but doesn't clarify what 'package_name' represents (e.g., a unique app identifier like 'com.example.app') or provide examples, leaving parameter meaning ambiguous despite the single parameter.

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 clearly states the action ('Clear') and target ('app data for a specific app on the connected Android device'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'uninstall_app' or 'stop_app', which also affect apps but in different ways, preventing a perfect score.

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 provides no guidance on when to use this tool versus alternatives like 'uninstall_app' (which removes the app entirely) or 'stop_app' (which halts execution). It also lacks prerequisites, such as needing an active Android device connection, leaving usage context unclear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vs4vijay/espresso-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server