mcp-systemctl

service_control

Start, stop, restart, reload, enable, or disable systemd services. Requires root/sudo for most actions.

Instructions

Control a systemd service: start, stop, restart, reload, enable, or disable. NOTE: Most actions require root/sudo privileges and will return a permission error if unavailable.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Service name (e.g. 'sshd', 'cron', 'nginx.service')
`action`	Yes	Action to perform on the service

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 18, 2026

TDQS

A4/5.0

Behavior3/5

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

The description discloses that most actions require root/sudo and may return permission errors. However, with no annotations provided, it does not cover other behavioral traits such as side effects on dependent services, action idempotency, or response format. This is adequate but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise: two sentences with no extraneous words. The first sentence states purpose and actions; the second adds crucial permission context. Every sentence earns its place.

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

Completeness4/5

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

Given the simple nature of the tool (2 params, no output schema, no annotations), the description covers the main actions and a critical permission note. It does not explain success/failure output or naming conventions, but it is nearly complete for a systemd control tool.

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% with both parameters described in the schema. The description does not add new semantic information beyond restating the action enum and the service name concept. Baseline score of 3 is appropriate.

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 clearly states the verb 'control' and the resource 'systemd service', listing the exact actions (start, stop, restart, etc.). This distinguishes it from sibling monitoring tools like get_service_logs and get_service_status.

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

Usage Guidelines4/5

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

The description includes a note about root/sudo privileges and permission errors, providing clear context on when the tool can be used. However, it does not explicitly mention when to use this tool versus alternatives like list_services or get_service_status.

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

Deploy Server