Skip to main content
Glama
Systems Manager

Systems Manager

Restart Service

sm_service_restart_service
Destructive

Restart a named system service to apply changes or recover from failures, using explicit confirmation for the mutating action when approval prompts are unavailable.

Instructions

Restart service (sm_service_operations). Operations for managing system services

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sm_service_restart_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.
service_nameNoName of the service

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the risk profile is known. The description adds nothing beyond that: it does not mention service downtime, in-flight connection loss, permission requirements such as root escalation, or how the confirm parameter factors into destructive execution.

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?

The first clause is tight and front-loaded, but the parenthetical and the generic second sentence 'Operations for managing system services' are boilerplate that occupies space without informing tool selection.

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?

For a destructive, non-idempotent mutation tool with no output schema, the description should warn about service disruption and describe expected response behavior. It supplies none of that, leaving the agent reliant solely on structured fields.

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%, so both parameters (service_name and confirm) are already documented in the schema, establishing a baseline of 3. The description contributes no additional meaning about service naming conventions or when to set confirm=true.

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 service'), which is enough to identify the operation. However, it never distinguishes this from close siblings such as manage_service_restart or sm_service_start_service, and the trailing phrase 'Operations for managing system services' adds no differentiating detail.

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 when-to-use guidance, no stated prerequisites, and no mention of alternatives such as start, stop, or the manage_service_restart sibling. An agent must infer the correct tool from the name alone.

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