Skip to main content
Glama

List Adb Processes

list_adb_processes
Idempotent

Lists running processes on a selected ADB device exactly as ps -A reports them, including user, PID, PPID, RSS, state, and name for instrumentation pairing. Read-only.

Instructions

List running processes exactly as ps -A reports them: user, pid, ppid, rss, state, and name. Useful for pairing with instrumentation lanes. Read-only.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serial": "emulator-5554"
    },
    "name": "list_adb_processes"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYesDevice serial exactly as `adb devices` reports it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior1/5

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

The description explicitly says 'Read-only,' while the annotations declare readOnlyHint=false. This is a direct contradiction about whether the tool can mutate state, and the extra detail about ps -A output does not resolve the conflicting safety profile.

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?

Two short sentences, front-loaded with the operation and output fields. The final 'Read-only' sentence is wasteful and misleading, but the overall structure is efficient.

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?

For a one-parameter list tool with no output schema, the description gives enough about what is returned and the ps -A equivalence. It omits device-targeting details, but those are fully covered by the schema.

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?

There is only one parameter (serial), and schema description coverage is 100%, including the exact 'adb devices' format. The description adds no parameter meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

States a specific verb (list) and resource (running processes), plus the exact fields returned by ps -A. It is clear enough to distinguish from generic listing tools, but it does not explicitly contrast with the closest sibling, list_frida_processes.

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

Usage Guidelines3/5

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

The phrase 'Useful for pairing with instrumentation lanes' implies a use case, but there are no explicit when-to-use rules, prerequisites, or alternatives such as list_frida_processes. Guidance is present but thin.

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