Skip to main content
Glama

renef_list_processes

Lists running userland processes with their PIDs and names on a rooted Android device, helping identify a target process for attachment.

Instructions

List running userland processes (pid + name) on the device, for renef_attach.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "renef_list_processes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add real scope information beyond the name — 'userland' excludes kernel-space entries and 'pid + name' bounds the payload — but it omits prerequisites such as whether a connected device/session is required and what happens when nothing is running.

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?

One front-loaded sentence with zero filler; the resource, the return fields, and the intended consumer all appear in the first clause. No restructuring would improve it.

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 zero-parameter list tool with an output schema, this is nearly complete — the return shape is documented by the schema and the description adds scope and purpose. The only missing piece is the connection/session prerequisite, which matters for an attach-oriented workflow tool.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline applies. The description correctly implies the call needs no arguments and is scoped implicitly to the connected device ('on the device').

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?

Specific verb (List) plus resource (running userland processes) and an explicit statement of what comes back (pid + name). It also names the sibling it feeds (renef_attach), so an agent can place it in a workflow without opening any 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?

The phrase 'for renef_attach' clearly signals the intended downstream use: run this first to obtain a pid to attach to. It stops short of any exclusion — it never says how it differs from renef_list_apps, which is the most plausible wrong pick for an agent looking for a process/app list.

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