Skip to main content
Glama
Systems Manager

Systems Manager

Disable Service

sm_service_disable_service
Destructive

Disable a named system service to stop it from running, with explicit confirmation for clients that cannot answer approval prompts.

Instructions

Disable 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_disable_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.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds no behavior beyond that: it does not explain whether disabling stops a running service, affects startup behavior, or what confirmation means.

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, front-loaded with the action. The parenthetical grouping and generic second sentence add little, but there is no serious bloat.

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

Completeness3/5

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

For a simple two-parameter destructive operation, annotations and schema cover the safety flags and parameter definitions. The description still omits the operational consequence of disabling a service and any confirmation requirement, leaving a gap for a mutation tool.

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 and service_name) are fully documented in the input schema. The description adds no parameter meaning, but baseline is 3 when the schema does the heavy lifting.

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 first phrase gives a specific verb and resource ('Disable service'), so the action is identifiable. However, the second sentence is generic ('Operations for managing system services') and does not differentiate this from siblings such as manage_service_disable or sm_service_stop_service.

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?

No guidance is given on when to choose this tool over manage_service_disable or when disabling rather than stopping a service is appropriate. The description states neither preconditions nor exclusions.

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