Systems Manager

Sm Process Operations

sm_process_operations

Manage system processes by listing running processes, retrieving process details, or terminating processes with PID and confirmation.

Instructions

Operations for managing system processes

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": {
      "action": "<action>"
    },
    "name": "sm_process_operations"
  }
}

Input Schema

Name	Required	Description
`pid`	No	Process ID
`action`	Yes	Action to perform. Must be one of: 'list_processes', 'get_process_info', 'kill_process'
`confirm`	No	Explicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.9Nov 3, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "description": "Explicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.",
+  "type": "boolean"
+}

First observedv2.2.5Oct 24, 2026

TDQS

C2.3/5.0

Behavior2/5

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

With no annotations, the description carries the entire behavioral burden and delivers almost nothing: it does not disclose that one action terminates processes irreversibly, that 'confirm' exists as a safety gate, or whether elevated privileges are required. An agent could invoke kill_process with no warning that destruction is possible.

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?

A single short sentence with no wasted words, but it is undersized rather than appropriately sized for a three-action tool hiding a destructive operation. Brevity here is a symptom of under-specification, not efficiency.

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?

No annotations and no output schema mean the description must explain the mutation risk, the confirm requirement, and what each action returns; it explains none of these. For a tool that can kill processes, this is a significant completeness gap.

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 100%, so the action enum and the confirm flag are already documented in the schema. The description adds no meaning beyond it — notably nothing about the interplay of pid with each action or that confirm is only meaningful for mutating actions. Baseline 3 applies.

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?

The description restates the title almost verbatim ('Operations for managing system processes') without naming a specific verb or distinguishing itself from siblings like get_process_details, list_services, or sm_system_operations. Only 'system processes' adds identifying information; the three distinct actions (list, inspect, kill) are invisible in the description.

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 guidance on when to choose this tool over get_process_details or sm_system_operations, and no guidance on which action to pick for which intent. The reader must open the schema to discover that the tool bundles listing, inspection, and termination.

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