Skip to main content
Glama
Systems Manager

Systems Manager

Start Service

manage_service_start
DestructiveIdempotent

Starts a system service after requesting confirmation, with explicit confirmation for clients that cannot answer an approval prompt.

Instructions

Start 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_start"
  }
}

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.2/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, so the safety profile is covered. The description adds the interactive confirmation step, which is genuinely new context, but says nothing about what happens on decline, on failure, or what state the service ends in.

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, action first and the confirmation caveat second, with no filler. Brevity is appropriate, though the confirmation sentence is left ambiguous about whether it applies when confirm=true.

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 cover the mutation/idempotency profile. Still, for a destructive operation the description leaves the confirm semantics and failure behavior underspecified relative to the tool's risk.

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%, including a clear description of the confirm flag as the non-interactive approval path, so the schema carries the parameter meaning. The description's confirmation sentence loosely reinforces confirm but adds no format, default, or interaction detail beyond it.

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?

"Start a system service" gives a specific verb plus resource, so an agent knows exactly what the tool acts on. It does not, however, distinguish itself from siblings such as sm_service_start_service or manage_service_restart, so an agent must compare names on its own.

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 statement of when to use this tool rather than manage_service_restart or sm_service_start_service, and no prerequisites or exclusions are given. The only guidance-adjacent sentence concerns confirmation, which is behavior, not usage routing.

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