Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Manage Service

manage_service

Control systemd units by starting, stopping, restarting, reloading, enabling, disabling, masking, or unmasking services; optionally use sudo for system units or target the user manager.

Instructions

Control a systemd unit.

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": "<name>"
    },
    "name": "manage_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesunit name ('.service' appended if missing)
sudoNoelevate for system units
userNoact on the user manager (no sudo needed)
actionYesstart | stop | restart | reload | enable | disable | mask | unmask | try-restart

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and provides almost nothing. It does not disclose that several supported actions are destructive or disrupting (stop, disable, mask), that sudo defaults to true, or what happens when the unit does not exist — all of which matter for a mutation tool.

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?

Five words with no wasted phrasing and the concept front-loaded, so it is not bloated. But the brevity is under-specification rather than economy — the single sentence omits something essential for a multi-action control tool.

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?

The output schema means return values need no explanation, but for a mutation tool with four parameters, no annotations, and destructive actions in its action set, the description is far too thin. An agent gets no warning about irreversible or service-disrupting operations.

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%, including the action list and the '.service' suffix rule, so the schema already documents all four parameters. The description adds no meaning beyond it; baseline 3 applies.

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

Purpose3/5

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

"Control a systemd unit" names a resource (systemd unit) and a generic verb (control), which is enough to distinguish it from read-only siblings like get_service_status and get_service_logs. However, "control" is vague on its own — the actual operations (start, stop, restart, enable, mask, etc.) only appear in the schema, not 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?

There is no guidance on when to reach for this tool versus get_service_status or get_service_logs, and no note that status/log inspection should precede blind control actions. No prerequisites (e.g., unit must exist, system vs user manager selection) are stated.

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