Skip to main content
Glama

Disable service

spm_disable_service

Stops a managed service and disables it from starting at login or boot, keeping its definition so it can be enabled again later.

Instructions

Stop a managed service and turn off start at login or boot, so it stays stopped until enabled again. Its definition is kept and spm_enable_service brings it back. Use spm_stop_service for a temporary stop, or spm_delete_service to remove it completely. For a scheduled job, this disables 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_disable_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.7/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=false. The description adds genuinely non-obvious behavior: the service definition is retained, the state persists until re-enabled, scheduled jobs have their timer disabled, and system scope requires root/Administrator. It is consistent with destructiveHint=false because the action is reversible via spm_enable_service. It stops short of describing the response or failure modes for a non-root attempt.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with what the tool does, followed by reversibility, alternatives, and the scope caveat in descending order of decision value. Every clause carries information an agent needs to choose or call the tool correctly; there is no filler.

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

Completeness5/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 full schema coverage and no output schema, the description covers the remaining unknowns: reversibility, persistence, privilege requirements, scheduled-job behavior, and sibling disambiguation. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns more by stating the default scope ('acts on the current user's services unless system is true') and the privilege consequence of setting system=true, which the schema only hints at. This is real added meaning about parameter impact rather than a restatement.

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?

The description opens with a specific verb+resource ('Stop a managed service and turn off start at login or boot') and immediately pins down the defining property: the stop is persistent. It explicitly distinguishes itself from spm_stop_service, spm_enable_service and spm_delete_service, so an agent can select it without inspecting 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?

It names the two most confusable alternatives and the exact condition that selects each ('spm_stop_service for a temporary stop', 'spm_delete_service to remove it completely'). It also states the guardrail for the one optional parameter ('only use system when the user asks for it'), leaving nothing to inference.

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