Skip to main content
Glama

install_app

Install APK applications on connected Android devices by specifying the app file path.

Instructions

Install an App APK on the connected Android device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_pathYes

Implementation Reference

  • Handler function for the 'install_app' tool. Installs an APK file on the connected Android device using the 'adb install' command. The @mcp.tool() decorator registers this function as an MCP tool, defining its schema implicitly via the function signature (app_path: str) -> str.
    @mcp.tool()
    def install_app(app_path: str) -> str:
        """Install an App APK on the connected Android device"""
        result = subprocess.run(["adb", "install", app_path], capture_output=True, text=True)
        if result.returncode != 0:
            raise RuntimeError(f"Error installing App: {result.stderr}")
        return f"App '{app_path}' has been installed successfully."
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. While it implies a write operation ('Install'), it doesn't specify critical details like whether this requires device permissions, if it overwrites existing apps, what happens on failure, or any side effects. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, clear sentence with no wasted words, making it easy to parse quickly. It's front-loaded with the core action and resource, which is ideal for efficient understanding by an AI agent.

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 that this is a mutation tool (installing an app) with no annotations, no output schema, and minimal parameter documentation, the description is incomplete. It doesn't cover behavioral aspects like permissions, error handling, or what to expect after installation, which are crucial for safe and effective use in an Android device context.

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?

The input schema has 1 parameter with 0% description coverage, and the tool description provides no additional information about the 'app_path' parameter. It doesn't explain what format the path should be (e.g., local file path, URL), what it represents, or any constraints, failing to compensate for the lack of schema documentation.

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 ('Install') and target resource ('an App APK on the connected Android device'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'start_app' or 'uninstall_app', but the verb 'Install' is specific enough to distinguish it from most other operations in the sibling list.

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 'start_app' (for launching) or 'uninstall_app' (for removal). It also doesn't mention prerequisites such as having a connected Android device or the APK file being accessible, leaving the agent to infer context from the tool name alone.

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