Skip to main content
Glama

Stop service

spm_stop_service

Stops a running managed service immediately while keeping its definition and enabled state. Use it to halt a service temporarily; use disable or delete to keep it stopped or remove it.

Instructions

Stop a running managed service for now. It keeps its definition and still starts again at the next login or boot if it is enabled; use spm_disable_service to keep it stopped, or spm_delete_service to remove it. For a scheduled job, this also stops its timer. Acts on the current user's services unless system is true; machine-wide services need root on Linux and macOS or an Administrator shell on Windows, so only use system when the user asks for it.

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

Input Schema

NameRequiredDescriptionDefault
nameYesManaged service name.
systemNoManage machine-wide services instead of the current user's. Requires root or Administrator; leave false unless the user asks for system scope.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / system / description
      Previous value: -"Manage machine-wide services instead of current-user services."New value: +"Manage machine-wide services instead of the current user's. Requires root or Administrator; leave false unless the user asks for system scope."
  2. First observedv0.3.9

TDQS

A4.1/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description adds real behavior on top of that: the service keeps its definition, restarts at next login/boot if enabled, and stopping a scheduled job also stops its timer. That is genuine disclosure of side effects and persistence semantics rather than a restatement of the safety flags.

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?

Front-loaded with the action, then the persistence consequence, then the alternatives, then the scope caveat — a logical order with no filler. The closing root/Administrator clause largely repeats the 'system' parameter description in the schema, a small redundancy.

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

Completeness4/5

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

For a two-parameter mutation tool with no output schema, it covers the important things: transience, restart-on-boot behavior, timer side effect, sibling alternatives, and privilege requirements. Minor gaps remain around what is returned on success and how an already-stopped or unknown service name is handled.

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 coverage is 100% and both parameters are already documented with defaults and prerequisites, so the schema carries the load. The description restates the user-vs-system scoping and the root/Administrator requirement rather than adding new syntax or edge-case meaning (e.g. what happens if the service is already stopped).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Stop a running managed service') and immediately qualifies the scope ('for now') so the agent knows the stop is transient rather than permanent. It then names the sibling tools that produce the other outcomes (spm_disable_service, spm_delete_service), making it distinguishable without opening any schema.

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

Usage Guidelines5/5

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

Explicitly routes between alternatives: use this for a temporary stop, spm_disable_service to keep it stopped, spm_delete_service to remove it. It also constrains the 'system' scope with a concrete rule ('only use system when the user asks for it') and states the privilege prerequisite.

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