Skip to main content
Glama
Systems Manager

Systems Manager

Disable at boot Service

manage_service_disable
DestructiveIdempotent

Disable a system service from starting at boot, with a confirmation step before applying the change.

Instructions

Disable at boot 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_disable"
  }
}

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

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds the confirmation-prompt behavior, which is genuinely beyond the annotations, but it does not say what state is lost (the boot registration), whether it requires elevation, or how failure is reported.

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 action stated first and the confirmation caveat second; nothing is wasted. It is arguably too terse for a destructive operation, but structure and front-loading are good.

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?

An output schema exists, so return values need not be described, and annotations carry the destructive/idempotent profile. Still, for a state-changing boot-configuration tool the description gives no prerequisite or side-effect detail to supplement the schema.

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%, so both parameters are already documented, and the baseline of 3 applies. The description's mention of confirmation loosely maps to the 'confirm' parameter but adds no clarification of the fallback case where a client cannot answer an approval prompt.

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 description states a specific verb and resource: 'Disable at boot a system service,' which is clearly distinct from enable/start/stop/restart siblings by naming the boot-time scope. It does not explicitly name or route against the near-duplicate sibling sm_service_disable_service, so it stops short of a 5.

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

Usage Guidelines3/5

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

The phrase 'Asks for confirmation first' implies an interactive approval flow, giving an agent some sense of when this tool requires a human in the loop. However, there is no explicit statement of when to prefer this over manage_service_stop or the sm_service_disable_service variant.

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