Skip to main content
Glama
Systems Manager

Systems Manager

Enable Service

sm_service_enable_service
Destructive

Enable a system service by specifying its name, with optional confirmation for clients that cannot answer approval prompts.

Instructions

Enable 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_enable_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.5/5.0
Behavior2/5

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

The annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say whether enabling persists across reboots, whether elevated privileges are required, what happens if the service does not exist, or how the mutation is confirmed. For a destructive mutation, this is a real gap.

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

Conciseness3/5

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

It is short and front-loads the action, which is good. However, the second sentence is pure restatement that could be deleted with no loss, and the parenthetical tag is unexplained noise rather than useful structure.

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

Completeness2/5

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

This is a destructive, non-idempotent state mutation with no output schema, so the description should explain the effect of enabling and any permission or persistence implications. Given the complexity and the destructive annotation, the definition is far too thin to let an agent invoke it confidently.

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 are documented in the schema, including the confirm flag's purpose. The description adds no meaning about service_name formatting or how confirm interacts with approval prompts, so it sits at the baseline where the schema carries the load.

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

Purpose3/5

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

"Enable service" gives a clear verb and resource, so the basic action is identifiable. But the parenthetical "(sm_service_operations)" is an opaque tag rather than a scope statement, and the second sentence ("Operations for managing system services") is generic filler that does nothing to separate this from siblings like manage_service_enable or sm_service_start_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?

There is no when-to-use guidance, no statement of preconditions, and no mention of any alternative. An agent must guess whether this is the right tool versus manage_service_enable or sm_service_start_service, and the description does nothing to resolve that overlap.

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