Skip to main content
Glama
rahulkr
by rahulkr

get_app_info

Retrieve detailed information about installed Android applications, including version, permissions, and activity data, for development and testing purposes.

Instructions

Get detailed information about an installed app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYes
device_serialNo

Implementation Reference

  • The main handler function for the 'get_app_info' tool. It is decorated with @mcp.tool(), which registers it as an MCP tool. The function extracts app information like version, install times, and target SDK from 'dumpsys package' output using regex.
    @mcp.tool()
    def get_app_info(package_name: str, device_serial: str | None = None) -> dict:
        """Get detailed information about an installed app"""
        dump = run_adb(["shell", "dumpsys", "package", package_name], device_serial)
        
        info = {"package": package_name}
        
        # Extract version
        version_match = re.search(r'versionName=(\S+)', dump)
        if version_match:
            info['version_name'] = version_match.group(1)
        
        version_code_match = re.search(r'versionCode=(\d+)', dump)
        if version_code_match:
            info['version_code'] = version_code_match.group(1)
        
        # First install time
        install_match = re.search(r'firstInstallTime=(.+)', dump)
        if install_match:
            info['first_install'] = install_match.group(1).strip()
        
        # Last update time
        update_match = re.search(r'lastUpdateTime=(.+)', dump)
        if update_match:
            info['last_update'] = update_match.group(1).strip()
        
        # Target SDK
        sdk_match = re.search(r'targetSdk=(\d+)', dump)
        if sdk_match:
            info['target_sdk'] = sdk_match.group(1)
        
        return info
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe any behavioral traits such as whether it requires specific permissions, what format the detailed information is returned in, or any potential side effects. This is a significant gap for a tool with no annotation coverage.

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, clear sentence with no wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance without unnecessary elaboration.

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 of retrieving app information, no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks details on what 'detailed information' includes, how to interpret parameters, or any behavioral context, making it inadequate for effective tool use.

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?

The schema description coverage is 0%, meaning parameters are undocumented in the schema. The description doesn't mention any parameters or provide meaning beyond the schema, failing to compensate for the coverage gap. It doesn't explain what 'package_name' or 'device_serial' represent or how they should be used.

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 ('Get') and resource ('detailed information about an installed app'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_device_info' or 'get_current_activity' that also retrieve information, so it doesn't reach the highest 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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools that retrieve various types of information (e.g., 'get_device_info', 'get_current_activity'), there's no indication of what makes this tool specific or when it should be preferred over others.

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