Skip to main content
Glama
cbxss
by cbxss

list_apps

List installed applications on a connected Android device to identify targets for security testing. Use optional device ID or default to USB connection.

Instructions

List installed applications on a device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idNoDevice ID (optional, defaults to USB)

Implementation Reference

  • The actual implementation of list_apps. Gets a Frida device (by device_id or USB default), enumerates installed applications, and returns a list of dicts with identifier, name, and pid.
    def list_apps(device_id: str | None = None) -> list[dict]:
        """List installed applications on a device."""
        if device_id:
            device = frida.get_device(device_id)
        else:
            device = frida.get_usb_device(timeout=5)
    
        apps = []
        for app in device.enumerate_applications():
            apps.append({
                "identifier": app.identifier,
                "name": app.name,
                "pid": app.pid if app.pid else None,
            })
        return apps
  • Tool registration definition for list_apps, including its name, description, and inputSchema (accepts optional device_id string).
    Tool(
        name="list_apps",
        description="List installed applications on a device",
        inputSchema={
            "type": "object",
            "properties": {
                "device_id": {"type": "string", "description": "Device ID (optional, defaults to USB)"},
            },
            "required": [],
        },
    ),
  • Dispatch/call_tool function that routes 'list_apps' requests to device.list_apps(), passing the device_id argument.
    elif name == "list_apps":
        return device.list_apps(arguments.get("device_id"))
  • Test file that verifies 'list_apps' is present in the expected CORE_TOOLS set.
    class TestExpectedTools:
        """Verify expected tools exist"""
    
        CORE_TOOLS = {
            "list_devices",
            "list_processes",
            "list_apps",
            "connect",
            "disconnect",
            "is_connected",
        }
Behavior2/5

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

With no annotations provided, the description must fully disclose behavior. It only states the action without detailing side effects, authorization needs, or return format. The tool likely reads device state, but this is not confirmed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single, efficient sentence with no redundancy. However, the brevity sacrifices necessary details for usage and transparency. It earns points for being concise but loses for not being more informative.

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 a simple tool with one optional parameter and no output schema, the description still lacks critical context such as the need for prior connection or how results are presented. It is minimally complete but leaves significant gaps.

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?

Schema coverage is 100% with a clear description for the optional device_id parameter. The description adds no new meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 action 'list' and the resource 'installed applications on a device', making the purpose unambiguous and distinct from sibling tools like list_devices or list_processes.

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 on when to use this tool versus alternatives such as list_processes or when a device connection is required. The description lacks any context about prerequisites or usage conditions.

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/cbxss/frida-mcp'

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