Skip to main content
Glama

mobile_launch_app

Launch Android applications using their package names to automate app management and testing workflows on mobile devices.

Instructions

Launch an application by its package name.

Args: package_name: The package name of the app to launch (e.g., 'com.android.chrome')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:252-268 (handler)
    The main handler function for the 'mobile_launch_app' tool. It is decorated with @mcp.tool(), which likely handles both registration and schema inference from the signature and docstring. The function launches an Android application by package name after verifying device initialization and app installation.
    def mobile_launch_app(package_name: str) -> str:
        """Launch an application by its package name.
        
        Args:
            package_name: The package name of the app to launch (e.g., 'com.android.chrome')
        """
        if device is None:
            return "Error: Device not initialized. Please call mobile_init() first to establish connection with Android device."
        try:
            apps = device.app_list()
            if package_name not in apps:
                return f"App {package_name} is not in the list of installed apps. Please use mobile_list_apps to get the current app list."
            
            device.app_start(package_name)
            return f"Successfully launched app: {package_name}"
        except Exception as e:
            return f"Error launching app {package_name}: {str(e)}"
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Launch') but lacks details on permissions needed, whether the app must be installed, error handling (e.g., if package_name is invalid), or system requirements. This is a significant gap for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, with the core purpose stated first and parameter details in a separate section. It avoids unnecessary words, though the structure could be slightly more integrated (e.g., merging the Args section into the main text).

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?

Given the tool's moderate complexity (a mutation with one parameter) and the presence of an output schema (which reduces the need to describe return values), the description is minimally adequate. However, it lacks behavioral details and usage guidelines, making it incomplete for safe and effective use.

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

Parameters4/5

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

The description adds meaningful context beyond the input schema, which has 0% coverage. It explains that package_name identifies the app to launch and provides an example ('com.android.chrome'), clarifying the parameter's purpose and format, though it doesn't cover all possible edge cases.

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 tool's purpose with a specific verb ('Launch') and resource ('application by its package name'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like mobile_init or mobile_list_apps, which prevents 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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., whether mobile_init must be called first), exclusions, or comparisons to siblings like mobile_click or mobile_list_apps, 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/erichung9060/Android-Mobile-MCP'

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