Skip to main content
Glama
Systems Manager

Systems Manager

List Processes

sm_process_list_processes
Read-onlyIdempotent

List running system processes to inspect activity and manage processes on a host.

Instructions

List processes (sm_process_operations). Operations for managing system processes

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing beyond that, and the phrase "managing system processes" mildly cuts against the read-only hint by implying mutation, though the leading "List processes" keeps it from being a true contradiction.

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 leading "List processes (sm_process_operations)" is front-loaded and functional. The second sentence, "Operations for managing system processes", is filler that duplicates the family title and adds no actionable information.

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

Completeness3/5

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

With no parameters, no output schema, and annotations covering the safety profile, the definition is minimally sufficient for invocation. It is still thin on what the returned process entries look like and whether filtering is possible, which would help an agent decide between this and get_process_info.

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

Parameters4/5

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

The tool takes zero parameters and the schema is empty, so there is nothing for the description to clarify. Baseline 4 applies to a no-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List processes" gives a concrete verb and resource, and the parenthetical ties it to the sm_process_operations family. However, the trailing sentence "Operations for managing system processes" restates the family rather than the tool, so it neither sharpens the purpose nor distinguishes this list operation from siblings like sm_process_get_process_info or sm_process_kill_process.

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?

The description gives no guidance on when to use this versus sm_process_get_process_info for a single process. It only implies usage through the word "List", leaving the agent to infer the distinction from siblings' names.

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