Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

manage_service

Destructive

Control systemd services on remote Linux servers via SSH: start, stop, restart, reload, enable, disable, or check status.

Instructions

Manage a systemd service. action: 'start', 'stop', 'restart', 'reload', 'enable', 'disable', 'status'.

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": {
      "server": "<server>",
      "service": "<service>",
      "action": "<action>"
    },
    "name": "manage_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
serverYes
serviceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, so the agent knows the tool mutates state. The description does not explain which actions are destructive versus read-only ('status' is clearly a safe read, 'stop'/'disable' take a service down), nor does it mention privilege requirements or whether actions are reversible.

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?

Two compact sentences with the resource named first and the action vocabulary front-loaded, no filler. It is terse to the point of under-specification rather than padded.

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?

Three required parameters, no output schema, and no annotation detail on parameters leave substantial gaps; the description never explains what 'server' refers to or what a 'status' call returns. For a destructive lifecycle tool this should say more about targets and effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry parameter meaning, and it only partly does: it enumerates the valid 'action' values, which is genuinely useful since no enum is declared in the schema. The 'server' and 'service' parameters receive no explanation at all — no unit-name format, no indication of whether server is a hostname, alias from list_servers, or session id.

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?

States a specific verb and resource ('Manage a systemd service') and enumerates the seven supported actions, so an agent knows the domain of operation. 'Manage' is generic and there is no differentiation from the sibling check_services, which overlaps semantically with the 'status' action.

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

Usage Guidelines3/5

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

The action list implies when to use it (start/stop/restart lifecycle control), but nothing states preconditions, when to prefer check_services for a read-only inspection, or whether the target service must already exist. Guidance is implied rather than explicit.

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