Skip to main content
Glama
Systems Manager

Systems Manager

Kill Process

sm_process_kill_process
DestructiveIdempotent

Terminate a running system process by specifying its process ID to stop unwanted or unresponsive tasks.

Instructions

Kill process (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_kill_process"
  }
}

Input Schema

NameRequiredDescriptionDefault
pidNoProcess ID
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.

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 destructiveHint=true, idempotentHint=true, openWorldHint=true, and readOnlyHint=false, so the safety profile is largely covered elsewhere. The description adds no behavioral context such as irreversibility, target scope, permission requirements, or effects of omitting pid.

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 definition is short and front-loads the action, but the second sentence is generic filler that does not help an agent invoke the tool. It could be more useful with a targeted safety or scope statement instead.

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 destructive process-killing tool with an optional pid parameter, the description does not explain what happens if pid is omitted, what processes may be affected, or how confirm relates to approval behavior. Annotations and schema provide some safety context, but the description leaves critical operational gaps.

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 schema already documents both pid and confirm. The description adds no meaning beyond that, which meets the baseline for high-coverage schemas, but it does not resolve the dangerous ambiguity of pid defaulting to null.

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?

The description states a specific verb and resource: "Kill process." It does not clearly differentiate from process inspection siblings like sm_process_get_process_info or sm_process_list_processes, and the trailing phrase "Operations for managing system processes" is too generic to add scope.

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 provides no when-to-use guidance, no warnings about termination being destructive, and no indication of when confirmation should be supplied. An agent must infer all usage conditions from annotations and schema alone.

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