Skip to main content
Glama
Systems Manager

Systems Manager

Enable at boot Service

manage_service_enable
DestructiveIdempotent

Enable a system service to start at boot and request confirmation before applying the change.

Instructions

Enable 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_enable"
  }
}

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.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds the approval-prompt behavior, which is useful context not in the annotations, but it never explains why enabling a boot service is destructive or what persistent state (unit symlinks, init config) is modified.

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, purpose front-loaded, no filler. The second sentence earns its place by flagging the interactive confirmation step, though it could be folded in more tightly.

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 and the parameter set is small, so the description needn't cover returns. However, for a destructive, persistent-configuration mutation it should say what 'enable at boot' actually changes and whether it requires elevated permissions, which it omits.

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 schema already documents both parameters well, including the confirm fallback for non-interactive clients. The description reinforces the confirmation flow, giving a small amount of added meaning without redundant detail.

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?

States a specific verb and resource ('Enable at boot a system service'), and the 'at boot' qualifier distinguishes it conceptually from start/restart siblings. It does not explicitly name manage_service_start or sm_service_enable_service, so the differentiation is implied rather than spelled out.

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 guidance on when to choose this over manage_service_start (run now) or sm_service_enable_service. The only usage-adjacent note is 'Asks for confirmation first,' which describes mechanics rather than selection criteria or prerequisites (e.g., root privileges).

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