Skip to main content
Glama
rahulkr
by rahulkr

launch_activity

Start a specific Android activity by providing package and activity names to launch app components for testing or development workflows.

Instructions

Launch a specific activity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYes
activity_nameYes
device_serialNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function decorated with @mcp.tool(), which registers it as an MCP tool. Launches a specific Android activity using ADB by constructing the component name and executing the 'am start' command.
    @mcp.tool()
    def launch_activity(
        package_name: str, 
        activity_name: str,
        device_serial: str | None = None
    ) -> str:
        """Launch a specific activity"""
        component = f"{package_name}/{activity_name}"
        return run_adb(["shell", "am", "start", "-n", component], device_serial)
Behavior1/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 but fails entirely. It doesn't mention if this is a read-only or destructive operation, what permissions or device states are required, potential side effects (e.g., app foregrounding), or error conditions. The description lacks any behavioral context beyond the basic action implied by the name.

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 extremely concise with a single sentence, 'Launch a specific activity', which is front-loaded and wastes no words. While this under-specifies the tool's functionality, it scores high on conciseness as every word contributes directly to the core idea without redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (likely an Android automation tool with 3 parameters), lack of annotations, 0% schema coverage, and presence of an output schema (which the description doesn't reference), the description is completely inadequate. It fails to explain purpose, usage, behavior, or parameters, leaving the agent with insufficient information to use the tool correctly in context with many sibling tools.

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

Parameters1/5

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

Schema description coverage is 0%, meaning none of the three parameters (package_name, activity_name, device_serial) are documented in the schema. The description adds no information about what these parameters mean, their formats, or examples (e.g., Android package names vs. activity classes). This leaves parameters completely unexplained, failing to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Launch a specific activity' is a tautology that essentially restates the tool name 'launch_activity' without adding meaningful specificity. It doesn't clarify what type of activity (e.g., Android app activity, system component) or distinguish it from sibling tools like 'launch_app' or 'get_current_activity', leaving the purpose vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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. There are no mentions of prerequisites, context (e.g., device state), or comparisons to sibling tools such as 'launch_app' or 'get_current_activity', making it misleadingly simplistic for a tool that likely requires specific conditions to function.

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