Skip to main content
Glama
Systems Manager

Systems Manager

Stop Service

manage_service_stop
DestructiveIdempotent

Stops a specified system service after confirmation to prevent unintended shutdowns.

Instructions

Stop 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_stop"
  }
}

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

C2.9/5.0
Behavior2/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 covered. The description's single behavioral note ("asks for confirmation first") merely restates what the schema's confirm parameter already documents, and it says nothing about graceful vs forced shutdown, dependent services, or required privileges.

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 with the operation stated first and the confirmation behavior second; nothing is padded. It is arguably too terse rather than wasteful, but structure and front-loading are sound.

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?

An output schema exists so return values need no explanation, but for a destructive mutation the description should say more about irreversibility, impact on running dependents, or privilege requirements. An agent can invoke it, but not confidently predict consequences.

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 are documented, including the non-obvious confirm flag for clients that cannot answer an approval prompt. The description adds no meaning beyond that, so the baseline of 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?

"Stop a system service" names a specific verb and resource, so the agent knows exactly what operation this performs. It does not differentiate from nearby siblings such as manage_service_restart, manage_service_disable, or sm_service_stop_service, leaving ambiguity about which stop variant to pick.

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 use this versus disable, restart, or the sm_ prefixed stop sibling. The only usage-adjacent statement is that confirmation is requested, which is workflow mechanics rather than selection guidance.

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