Skip to main content
Glama

Delete service

spm_delete_service
Destructive

Permanently stop a managed service and delete its definition, saved configuration, and companion units such as schedules and health checks. Confirm the exact name and scope first; this action cannot be undone.

Instructions

Stop a managed service and permanently remove its definition, saved configuration and companion units such as schedules and health checks. This cannot be undone; the service must be created again with spm_create_service. Confirm the exact name and scope with the user first, and prefer spm_stop_service or spm_disable_service when the user may need it again. 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_delete_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.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds substantial detail beyond them: exactly what is destroyed (definition, saved configuration, companion units such as schedules and health checks), that the action is irreversible, the recovery path (recreate via spm_create_service), and the privilege requirements for system scope. The only gap is that it doesn't say whether the effect is immediate or whether the service must be stopped first.

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?

Three sentences, front-loaded with the destructive effect and irreversibility before caveats and alternatives. Every clause carries actionable information; nothing is 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 destructive tool with no output schema, the description covers what is destroyed, irreversibility, recovery, permission requirements and safer alternatives. An agent has everything needed to decide whether to call it and how to set the scope flag.

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 the schema's own parameter descriptions already state the root/Administrator requirement and 'leave false unless the user asks for system scope', which the description largely restates. It does add the useful default-scope framing ('acts on the current user's services unless system is true'), so this is at or slightly above the baseline.

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 compound verb and resource: stop the service and permanently remove its definition, saved configuration and companion units (schedules, health checks). This is clearly distinguished from spm_stop_service and spm_disable_service, which are named as the non-destructive alternatives.

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 says when not to use it ('prefer spm_stop_service or spm_disable_service when the user may need it again'), requires confirming name and scope with the user first, and restricts 'system' to cases where the user asks for machine-wide scope. Alternatives and preconditions are both spelled out.

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