Skip to main content
Glama

list_processes

Read-onlyIdempotent

Read account-visible QNX threads and IPC wait evidence to diagnose process state and distinguish idle receivers from real IPC dependency cycles.

Instructions

Read account-visible QNX threads and IPC wait evidence. Peer TID and hidden processes may be unavailable.

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": "list_processes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pidNo
nameNo
limitNoMaximum number of thread rows

Output Schema

NameRequiredDescriptionDefault
dataYes
statusYes
warningsNo
target_idYes
truncatedNo
observed_atYes
schema_versionNo1.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds genuine value beyond that by disclosing visibility scoping ("account-visible") and known data gaps ("Peer TID and hidden processes may be unavailable"), which tells the agent results can be partial. It stops short of explaining pagination interaction with those gaps, result ordering, or what "IPC wait evidence" actually contains.

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 tight sentences with the capability statement front-loaded and the caveat second; nothing is redundant. It is arguably too terse given the undocumented parameters, but brevity itself is not the problem here.

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?

An output schema exists, so return-value explanation is not required, but the definition leaves key gaps for a tool with three filtering parameters: no explanation of pid/name semantics or their interaction, and no guidance on choosing this tool over system_info. The visibility caveat is helpful, yet the description does not fully equip an agent to invoke it correctly with filters.

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 only 33% — only the limit parameter is documented ("Maximum number of thread rows"), while pid and name carry no explanatory text in either schema or description. The description does not clarify whether pid and name are combined with AND logic, whether name is a substring or exact match, or whether filtering by pid returns all threads of that process. With low coverage, this is a real gap.

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?

The description pairs a specific verb ("Read") with a concrete resource ("account-visible QNX threads and IPC wait evidence"), so an agent knows it retrieves thread/process inspection data rather than files or logs. It does not explicitly name how it differs from siblings like system_info, and the "threads" wording sits slightly awkwardly against the tool name "list_processes", but the resource is distinct enough to route on.

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?

There is no when-to-use guidance, no mention of alternatives such as system_info or read_system_log, and no indication of when pid, name, or limit filtering is appropriate. The only contextual hint is the "account-visible" scope, which implies limitations but not selection criteria.

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