Skip to main content
Glama
rahulkr
by rahulkr

list_packages

List installed packages on Android devices with optional filtering by name or system status to identify applications for development, testing, or debugging workflows.

Instructions

List installed packages, optionally filtered

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filter_textNo
include_systemNo
device_serialNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function that implements the logic for the 'list_packages' MCP tool. It executes ADB commands to list installed packages, filters them based on parameters, and returns a sorted list of package names.
    @mcp.tool()
    def list_packages(
        filter_text: str = "", 
        include_system: bool = False,
        device_serial: str | None = None
    ) -> list[str]:
        """List installed packages, optionally filtered"""
        args = ["shell", "pm", "list", "packages"]
        if not include_system:
            args.append("-3")  # Third-party only
        
        output = run_adb(args, device_serial)
        packages = [line.replace("package:", "").strip() 
                    for line in output.split('\n') if line.strip()]
        
        if filter_text:
            packages = [p for p in packages if filter_text.lower() in p.lower()]
        
        return sorted(packages)
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 mentions filtering capability but doesn't disclose important behavioral traits: whether this requires specific permissions, how results are formatted/paginated, if it's a read-only operation, performance characteristics, or what happens when no packages match. The description is minimal and leaves critical operational details unspecified.

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 (5 words) and front-loaded with the core purpose. Every word earns its place, with no redundant information or unnecessary elaboration.

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 (3 parameters, no annotations, but with an output schema), the description is minimally adequate. The existence of an output schema means return values don't need explanation, but the description should provide more context about the tool's behavior, usage scenarios, and parameter meanings to be truly complete.

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

Parameters3/5

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

With 0% schema description coverage, the description doesn't add any parameter-specific information beyond the generic 'optionally filtered' hint. It doesn't explain what 'filter_text' matches, what 'include_system' means, or when 'device_serial' is needed. However, the parameters have clear titles in the schema, providing some baseline understanding.

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 verb ('List') and resource ('installed packages'), and specifies optional filtering. However, it doesn't distinguish this tool from potential sibling package management tools (none exist in the sibling list, but the description doesn't explicitly note this uniqueness).

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. While there are no obvious package-related siblings, it doesn't mention prerequisites, timing considerations, or relationships with other tools like 'get_app_info' or 'uninstall_app' that might be used in similar contexts.

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