Skip to main content
Glama
nucleusv

Linux MCP daemon

by nucleusv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

processes/delete

Destructive

Send a signal to a process by PID to terminate, pause, or resume it. Default SIGTERM asks the process to exit; supports SIGKILL, SIGSTOP, SIGCONT, and others.

Instructions

Sends ONE signal to ONE process by PID (kill(2)); the default SIGTERM asks the process to exit. Mutating and not idempotent: it returns as soon as the signal is delivered and does not check that the process exited, and signalling a PID that is gone fails with no such process. Allowed signal values: SIGTERM, SIGKILL, SIGHUP, SIGINT, SIGQUIT, SIGUSR1, SIGUSR2, SIGSTOP, SIGCONT, SIGABRT (SIG prefix optional, case-insensitive, numbers rejected), so it can also pause (SIGSTOP) and resume (SIGCONT). Refuses PID 1 and the mcpd daemon itself. Another user's process fails with not permitted unless privileged: true (needs a grant). Find the PID first with processes/list or processes/top. To stop a managed service use services/manage (systemd may restart a killed one), for a container docker/manage. Returns one text line, Successfully sent signal SIGTERM to process N; output_format has no effect.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pidYesPID to signal (positive integer; PID 1 and mcpd itself are refused)
signalNoSIGTERM (default), SIGKILL, SIGHUP, SIGINT, SIGQUIT, SIGUSR1, SIGUSR2, SIGSTOP, SIGCONT or SIGABRT; SIG prefix optional, case-insensitive
privilegedNoRun as root to signal other users' processes. Needs a grant for this tool in mcp-sudo.yaml, otherwise refused
output_formatNoIgnored - the reply is always text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.1
    • changedInput schema / properties / output_format / description
      Previous value: -"Desired output format (e.g. json, yaml, table, wide). Defaults to text"New value: +"Ignored - the reply is always text"
    • changedInput schema / properties / pid / description
      Previous value: -"The PID to kill"New value: +"PID to signal (positive integer; PID 1 and mcpd itself are refused)"
    • changedInput schema / properties / privileged / description
      Previous value: -"Run as root to kill other user's processes"New value: +"Run as root to signal other users' processes. Needs a grant for this tool in mcp-sudo.yaml, otherwise refused"
    • changedInput schema / properties / signal / description
      Previous value: -"Signal to send (e.g., SIGTERM, SIGKILL)"New value: +"SIGTERM (default), SIGKILL, SIGHUP, SIGINT, SIGQUIT, SIGUSR1, SIGUSR2, SIGSTOP, SIGCONT or SIGABRT; SIG prefix optional, case-insensitive"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructiveHint/not-idempotent, and the description goes well beyond them: it states the signal is fire-and-forget with no exit verification, documents failure modes ('no such process', 'not permitted'), refusal of PID 1 and mcpd, the privileged-grant requirement, and that output_format is ignored. This is unusually rich behavioural disclosure.

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?

Front-loaded with the core action and default, then constraints and alternatives. It is dense and long for a single-signal tool, but nearly every sentence adds a distinct operational fact, so little is wasted.

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

Completeness5/5

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

Despite the absence of an output schema, the description specifies the exact return line ('Successfully sent signal SIGTERM to process N') and notes output_format has no effect. Combined with the error and permission notes, nothing an agent needs to call this correctly is missing.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds genuinely new constraint information: numbers are rejected as signal values, the SIG prefix is optional and case-insensitive, and privileged requires a grant from mcp-sudo.yaml. Only minor duplication of enum values keeps it from a 5.

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

Purpose5/5

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

The description names the exact operation (send ONE signal to ONE process by PID via kill(2)), its default behaviour (SIGTERM), and explicitly distinguishes itself from siblings like processes/list, processes/top, services/manage and docker/manage. An agent can identify this tool's role without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance ('Find the PID first with processes/list or processes/top') and when-not-to-use alternatives ('To stop a managed service use services/manage ... for a container docker/manage'), including the reason (systemd may restart a killed one). Routing is fully specified.

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