Skip to main content
Glama

list_apps

Display all installed applications on a connected Android device to manage or audit software inventory.

Instructions

List all installed apps on the connected Android device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_apps' tool, decorated with @mcp.tool(). It executes 'adb shell pm list packages' to list installed apps on the Android device and processes the output into a list of package names.
    @mcp.tool()
    def list_apps() -> list:
        """List all installed apps on the connected Android device"""
        result = subprocess.run(
            ["adb", "shell", "pm", "list", "packages"], capture_output=True, text=True
        )
        if result.returncode != 0:
            raise RuntimeError(f"Error listing installed apps: {result.stderr}")
        apps = [line.replace("package:", "").strip() for line in result.stdout.splitlines()]
        return apps
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action but lacks behavioral details: it doesn't specify if this requires device permissions, the format of returned data (e.g., list structure, app details), potential errors (e.g., if device is disconnected), or side effects. The description is minimal and misses key operational context.

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 no wasted words. It front-loads the core action ('List all installed apps') and specifies the context ('on the connected Android device') efficiently. Every part of the sentence contributes essential information.

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 the complexity (a read operation with device interaction) and lack of annotations or output schema, the description is incomplete. It doesn't explain what the output contains (e.g., app names, packages, versions) or behavioral aspects like error handling. For a tool that interacts with an external device, more context is needed for 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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing on the tool's purpose instead. This aligns with the baseline for zero-parameter tools, though it doesn't add extra semantic value beyond the schema.

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

Purpose5/5

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

The description clearly states the specific action ('List all installed apps') and the target resource ('on the connected Android device'), using precise verb+resource phrasing. It effectively distinguishes this tool from siblings like 'install_app' or 'uninstall_app' by focusing on enumeration rather than modification.

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. It doesn't mention prerequisites (e.g., device connectivity), exclusions, or related tools like 'list_avds' or 'list_emulators' for device management. Usage is implied but not explicitly defined.

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