Skip to main content
Glama
Systems Manager

Systems Manager

Restart Service

manage_service_restart
DestructiveIdempotent

Restart a system service, requesting confirmation first; use the confirm flag when the client cannot answer an approval prompt.

Instructions

Restart a system service. Asks for confirmation first.

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": {
      "service_name": "<service_name>"
    },
    "name": "manage_service_restart"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation. Pass true when the client cannot answer an approval prompt.
service_nameYesName of the service

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is largely structured. The description adds real value by disclosing that an approval prompt is raised before the action, which is not visible in annotations, but it omits the operational consequence (service downtime, dependent services) that matters for a destructive restart.

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 short sentences, action first and the confirmation caveat second, with no filler. The brevity is close to under-specification for a destructive operation, but nothing is wasted.

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

Completeness3/5

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

An output schema exists and annotations cover the safety hints, so those are not required in prose. What remains missing for a destructive tool is the blast radius — that restarting interrupts the service and may affect dependents — leaving the definition adequate but thin for the risk involved.

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% and the confirm parameter is already self-documenting ("Pass true when the client cannot answer an approval prompt"). The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 names a specific verb and resource ("Restart a system service"), which is enough for an agent to distinguish it from start/stop/enable/disable siblings by verb alone. It stops short of explicitly contrasting itself with those siblings, so no credit for full differentiation.

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?

No when-to-use or when-not-to-use guidance is given relative to manage_service_start, manage_service_stop, or the duplicate sm_service_restart_service. "Asks for confirmation first" describes a mechanic, not a selection criterion, so an agent learns nothing about which tool to pick.

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