Skip to main content
Glama
boy-offi9-inc

HexForge Gateway

by boy-offi9-inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

frida_list_processes

Read-only

List running processes on a device via Frida, optionally with installed apps, to find a PID or package name for frida_trace. Read-only.

Instructions

List running processes on a device via Frida, or with includeApps the installed apps too. Only reads. Use it to find the package name or PID to pass to frida_trace. Returns { processes: [...] } where each entry is { pid, name } or, with includeApps, { pid, name, identifier } - identifier is the package name, and an installed app that isn't running has no real PID. Requires frida-tools on PATH and a frida-server on the device whose version matches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceNoWorkspace name (not id). Created if it doesn't exist, and this call is recorded as a job in its history. Defaults to "default".
includeAppsNoAlso list installed apps with their package identifiers, not just running processes (frida-ps -a). Default false.
deviceSerialNoDevice serial from adb_devices, e.g. "emulator-5554" or "R58M123ABC". Only needed when more than one device is connected; omit otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.3.7
    • addedInput schema / properties / deviceSerial / description
      Added value: +"Device serial from adb_devices, e.g. \"emulator-5554\" or \"R58M123ABC\". Only needed when more than one device is connected; omit otherwise."
    • addedInput schema / properties / includeApps / default
      Added value: +false
    • changedInput schema / properties / includeApps / description
      Previous value: -"List installed apps, not just running processes"New value: +"Also list installed apps with their package identifiers, not just running processes (frida-ps -a). Default false."
    • changedInput schema / properties / workspace / description
      Previous value: -"Workspace name (not id) - created automatically if it doesn't exist yet. Defaults to \"default\"."New value: +"Workspace name (not id). Created if it doesn't exist, and this call is recorded as a job in its history. Defaults to \"default\"."
  2. First observedv1.3.0

TDQS

A4.3/5.0
Behavior4/5

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

"Only reads" merely restates readOnlyHint=true. The value-add is the undisclosed-by-annotations operational context: frida-tools must be on PATH and a version-matched frida-server must run on the device, both of which cause failures an agent should anticipate. It does not cover rate limits or failure modes beyond the prerequisite note.

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?

Front-loaded with the core action, then usage routing, then return shape, then prerequisites. Three dense sentences with little waste, though the return-shape sentence is long and slightly packs two shapes together.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description appropriately documents the return shape ({ pid, name } / { pid, name, identifier }) and the required runtime prerequisites. The only gap is the workspace parameter's side effect of creating a workspace and recording a job, which the description omits but the schema covers.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics the schema does not: the identifier field is the package name and an installed-but-not-running app has no real PID. That resolves genuine ambiguity about includeApps output. workspace and deviceSerial are left entirely to 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?

States a specific verb and resource ("List running processes on a device via Frida") plus the scope variant (includeApps adds installed apps). It also distinguishes itself from the sibling frida_trace by naming the handoff relationship, so an agent can tell the two apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use it to find the package name or PID to pass to frida_trace" gives an explicit situation and names the downstream alternative. It stops short of stating when NOT to use it (e.g., when a PID is already known), so it is clear context rather than full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools