Skip to main content
Glama
Systems Manager

Systems Manager

Stop Service

sm_service_stop_service
Destructive

Stops a named system service to halt its running processes. Provide the service name and set confirmation when the client cannot answer an approval prompt.

Instructions

Stop 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_stop_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, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing on top of that — it doesn't say what happens to running processes, whether the service stays stopped across reboots, whether the operation blocks, or what a failure looks like. For a destructive mutation, that is a real gap.

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 action verb is front-loaded and the text is short, but the second sentence ('Operations for managing system services') is pure filler that restates the category rather than informing the caller. At two sentences, half the description earns no place.

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?

This is a destructive, non-idempotent mutation with no output schema, and the description says nothing about consequences, reversibility, required privileges, or post-stop verification. The combination of a nullable service_name and destructiveHint=true makes the silence riskier than the schema alone can mitigate.

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 both parameters (confirm, service_name) are documented in the schema itself, including the escalation case where the client cannot answer an approval prompt. The description contributes no additional meaning about either parameter, 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 opens with a specific verb+resource ('Stop service'), so the action is unambiguous. The trailing '(sm_service_operations). Operations for managing system services' is generic category filler that does nothing to distinguish it from siblings such as manage_service_stop, sm_service_restart_service, or sm_service_disable_service, which is why it falls short of a 5.

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 or when-not-to-use guidance, and no alternatives are named. An agent gets no signal about choosing this over manage_service_stop or sm_service_disable_service, nor about whether stopping is a prerequisite for other operations like removal or reconfiguration.

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