uninstall_app
Remove an installed app from a connected Android device by providing its package name.
Instructions
Uninstall an app from the connected Android device
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| package_name | Yes |
Remove an installed app from a connected Android device by providing its package name.
Uninstall an app from the connected Android device
| Name | Required | Description | Default |
|---|---|---|---|
| package_name | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. The description does not disclose behavioral traits such as irreversibility, required permissions, or side effects. For a destructive action, this is insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no wasted words. It is appropriately sized for a simple tool, though could include additional context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is minimal for a destructive action. It does not mention irreversibility, success conditions, or error scenarios. Fails to provide complete context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description adds no meaning beyond the parameter name 'package_name'. It does not explain how to find the package name or format.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action 'uninstall' and the resource 'app from the connected Android device'. It distinguishes itself from sibling tools like 'install_app' and 'list_apps'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives, e.g., 'clear_app_data' for clearing data instead of uninstalling. No mention of prerequisites or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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