Skip to main content
Glama

List Frida Processes

list_frida_processes
Idempotent

Lists processes visible on a selected Frida device or supplied remote endpoint, then closes remote connections after discovery without returning or recording authentication values.

Instructions

List processes observed on a selected Frida device or caller-supplied remote endpoint. A remote connection is closed after discovery; authentication values are never returned or recorded.

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": {
      "device_id": "local"
    },
    "name": "list_frida_processes"
  }
}

Input Schema

NameRequiredDescriptionDefault
remoteNo
device_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Adds genuine context beyond the annotations: the remote connection is closed after discovery and authentication values are never returned or recorded, which speaks to lifecycle and credential handling. However, it never explains the readOnlyHint=false implication (that contacting a remote endpoint is treated as a side-effecting call) nor what is returned, so the disclosure is partial.

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?

Two front-loaded sentences with no filler; the scoping clause and the remote-lifecycle caveat each carry information the agent cannot get from structured fields.

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?

With zero schema description coverage, no output schema, and two optional parameters, the description needs to carry more weight. It omits what a process entry looks like, what happens when device_id is omitted, and the meaning of the remote sub-fields, leaving key calling decisions to guesswork.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and largely does not. 'Caller-supplied remote endpoint' gestures at the nested remote object, but device_id is never explained, no default behavior is given when neither parameter is supplied, and token/origin/certificate/keepalive_interval semantics are untouched.

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 and resource ('List processes') and scopes it to 'a selected Frida device or caller-supplied remote endpoint', which distinguishes it from list_adb_processes by target type. It does not explicitly contrast with list_frida_devices, but the resource noun carries the differentiation.

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?

Usage is only implied: 'observed on a selected Frida device' suggests a device must already be chosen, hinting at list_frida_devices as a prerequisite. There is no explicit statement of when to prefer this over list_adb_processes, nor when to supply device_id versus remote.

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