Skip to main content
Glama
cbxss
by cbxss

list_processes

Retrieve a list of running processes on a target device for mobile security testing. Specify a device ID to focus on a specific device or use USB connection by default.

Instructions

List running processes on a device

Input Schema

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

Implementation Reference

  • Schema definition for the list_processes tool, declaring name, description, and input schema with optional device_id parameter.
    Tool(
        name="list_processes",
        description="List running processes on a device",
        inputSchema={
            "type": "object",
            "properties": {
                "device_id": {"type": "string", "description": "Device ID (optional, defaults to USB)"},
            },
            "required": [],
        },
    ),
  • Core handler function that lists running processes on a Frida device (specified by device_id or default USB device).
    def list_processes(device_id: str | None = None) -> list[dict]:
        """List processes on a device."""
        if device_id:
            device = frida.get_device(device_id)
        else:
            device = frida.get_usb_device(timeout=5)
    
        processes = []
        for proc in device.enumerate_processes():
            processes.append({
                "pid": proc.pid,
                "name": proc.name,
            })
        return processes
  • Dispatch routing in call_tool() that maps the 'list_processes' tool name to the device.list_processes() handler.
    elif name == "list_processes":
        return device.list_processes(arguments.get("device_id"))
Behavior2/5

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

With no annotations, the description should disclose behavioral traits like output format, authentication requirements, or prerequisites. It only states the basic action, lacking sufficient transparency.

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, concise sentence that front-loads the essential information with no wasted words.

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 simplicity (1 optional param, no output schema), the description covers the basic purpose but lacks hints about the output structure or behavior, making it minimally 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?

The schema coverage is 100%, and the tool description does not add extra meaning beyond the schema's parameter description. Baseline 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 verb ('List'), resource ('running processes'), and scope ('on a device'), which distinguishes it from sibling tools like 'list_apps' and 'list_devices'.

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, such as when specific process details are needed or when connected to a device.

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