Skip to main content
Glama

processes

List, sort, and kill system processes by memory or CPU, filter by name, and find which process listens on a port or all open ports.

Instructions

Processes by memory/cpu (name filter), who listens on a port, all listening ports, kill a PID tree.

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

Input Schema

NameRequiredDescriptionDefault
opNo
pidNo
topNo
nameNo
portNo
sortNo
forceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It mentions 'kill a PID tree', hinting at destructive scope, but never states that killing is irreversible, whether 'force' is needed, what permissions are required, whether 'top' limits results, or what the response contains. For a tool that can terminate processes, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single-line fragment contains no filler, but it is compressed past the point of usefulness: capabilities are strung together with parentheticals rather than structured by operation, which makes it harder to map to the op enum.

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?

A 7-parameter tool with zero annotations, zero schema descriptions, and no output schema demands far more than one sentence. Mode-to-parameter relationships, defaults, result limits, and the destructive nature of kill all remain undocumented.

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% across 7 parameters, so the description must compensate and only partly does: it implies pid, port, name, sort (memory/cpu) and the op modes. It says nothing about 'top' (presumably a result limit), nothing about 'force', and never states which parameters pair with which op value, leaving several parameters meaningless to an agent.

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 names concrete capabilities: sorting processes by memory/cpu with a name filter, identifying which process listens on a port, listing all listening ports, and killing a PID tree. That is enough for an agent to recognize the tool's domain without opening the schema, though it is a terse fragment with no explicit differentiation from sibling utilities like net or disk_usage.

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 four listed modes imply when each capability applies, but there is no explicit guidance on choosing between them, no mapping of modes to the 'op' enum values, and no warnings about when killing is appropriate versus listing.

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