Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

process_list

Read-only

Lists top running processes on a remote Linux server by CPU or memory usage, helping identify resource-heavy services for troubleshooting or performance checks.

Instructions

List top processes sorted by CPU or memory usage. sort_by: 'cpu' or 'memory'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "server": "<server>"
    },
    "name": "process_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYes
sort_byNocpu

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description needs only add context — and it adds none beyond the sort values. It doesn't say how many processes 'top' returns, whether it's a snapshot or live sample, or what permissions/failure modes apply.

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 short sentences, conclusion first, with the legal sort values immediately actionable. Minor redundancy in restating 'sorted by CPU or memory' and then repeating the same options as sort_by values.

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?

For a two-parameter tool with no output schema and no annotation detail beyond read-only, the definition leaves key gaps: the semantics of the required server argument and the meaning/count of 'top' processes. Adequate to guess at, but not complete enough to call reliably without trial.

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

Parameters3/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. It usefully declares the allowed sort_by values ('cpu' or 'memory') that the schema itself leaves as an unconstrained string, but it says nothing about the required 'server' parameter — which server identifier format is expected or where to get it.

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+resource: lists processes, with the sort dimension (CPU or memory) named up front. It is clearly distinguishable from siblings like check_services or docker_ps, though it doesn't explicitly contrast with them.

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?

Implies usage (inspect resource-heavy processes on a host) but gives no when-to-use vs alternatives, and no prerequisites such as needing an active session or a valid server value before calling.

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