Skip to main content
Glama
rahulkr

Enhanced ADB MCP Server

by rahulkr
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

launch_app

Launch Android applications by package name using ADB commands. This tool starts apps on connected devices for development, testing, and debugging workflows.

Instructions

Launch an app by package name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYes
device_serialNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/adb_mcp_server/server.py:587-594 (handler)
    Handler function for the 'launch_app' tool. Launches the specified Android app package using the ADB 'monkey' command with LAUNCHER intent. The @mcp.tool() decorator registers this function as an MCP tool.
    @mcp.tool()
def launch_app(package_name: str, device_serial: str | None = None) -> str:
    """Launch an app by package name"""
    return run_adb([
        "shell", "monkey", "-p", package_name,
        "-c", "android.intent.category.LAUNCHER", "1"
    ], device_serial)

Tool Definition Quality

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose success/failure conditions, permissions needed, side effects (e.g., app foregrounding), or error handling, leaving critical operational context unspecified 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.

Conciseness5/5

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

The description is a single, direct sentence with zero wasted words, front-loading the core action and resource. It's appropriately sized for the tool's apparent simplicity, achieving maximum clarity per character without redundancy or fluff.

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 no annotations, 0% schema coverage, and a mutation tool with an output schema (unseen), the description is incomplete. It lacks behavioral context, parameter guidance, and fails to address complexity like multi-device handling or error scenarios, leaving the agent under-informed for safe invocation.

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 but adds no parameter details beyond the tool name. It mentions 'package_name' implicitly but doesn't explain format or examples, and ignores 'device_serial' entirely, failing to clarify semantics for both parameters.

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 ('Launch') and target resource ('an app by package name'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'launch_activity' or 'start_screen_record', but it's specific enough to convey core functionality without being tautological.

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 like 'launch_activity' or 'check_flutter_app_running'. The description lacks context about prerequisites (e.g., device connectivity) or exclusions, offering only basic functional intent without situational advice.

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/rahulkr/r_adb_mcp_server'

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