Skip to main content
Glama
Sign In
AI Process Manager

AI Process Manager

by aipm-engine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_processes

Read-only

List running processes sorted by CPU usage, with configurable limits and optional full command-line details.

Instructions

List running processes sorted by CPU. Use "top" to limit (default 25, max 200). Prefer check_process when searching for one process. Command lines truncated unless full_command_line=true.

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
topNoHow many processes to return (default 25)
full_command_lineNotrue for full command lines

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A5/5.0
Behavior5/5

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

Discloses key behavioral traits: processes are sorted by CPU, command lines are truncated unless full_command_line=true, and top has a default of 25 and max of 200. These go beyond the read-only and non-destructive annotations, adding valuable context.

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?

The description is two sentences, front-loaded with the main purpose, and every sentence adds useful information with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given only two parameters and no output schema, the description covers purpose, usage, behavioral details, and parameter semantics comprehensively. It is sufficient for an agent to select and invoke the tool correctly.

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

Parameters5/5

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

Even though the schema already describes both parameters, the description adds crucial details: top's default and max values, and the condition for full command lines. This significantly enriches the parameter meaning.

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?

The description clearly states the tool lists running processes sorted by CPU, using a specific verb and resource. It also differentiates from sibling tool check_process, which is for searching a single process.

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

Usage Guidelines5/5

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

Explicitly advises using check_process instead when searching for one process, and provides guidance on the top parameter with default and max values. This gives clear context on when and how to use the tool.

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