Skip to main content
Glama
Systems Manager

Systems Manager

Get Process Info

sm_process_get_process_info
Read-onlyIdempotent

Retrieve detailed information about a system process, optionally by PID, to inspect status and enable effective process management.

Instructions

Get process info (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_get_process_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
pidNoProcess ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, which sets a low bar, but the description adds nothing beyond them — notably it never explains that openWorldHint implies it reads live system state. It also does not say what is returned or what happens when pid is null.

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?

It is short and front-loaded, but the second sentence is filler that repeats no actionable information, and the parenthetical family tag adds nothing for tool selection.

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?

With no output schema, the description should have explained what a process-info lookup returns and how an omitted pid behaves; instead it leaves both open. For a tool with a live-system, open-world read, the definition is too thin to call correctly with confidence.

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 coverage is 100% for the single optional 'pid' parameter, so baseline 3 applies; the description contributes no additional meaning such as whether a null pid means 'current process' or a full process table.

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

Purpose2/5

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

"Get process info" restates the name and title almost verbatim; the second sentence ("Operations for managing system processes") is generic family boilerplate rather than a statement of what this specific call does. Nothing distinguishes it from a sibling like get_process_details or sm_process_list_processes.

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?

No when-to-use guidance is present: no mention of when to choose this over the listing or killing tools in the same family, and no indication of what omitting the optional pid yields. The agent must infer usage purely from the name.

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