Skip to main content
Glama
Systems Manager

Systems Manager

Start Service

sm_service_start_service
Destructive

Start a specified system service by name to bring required services online for system management and orchestration tasks.

Instructions

Start 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_start_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?

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond them — no note on what starting a service changes, whether it fails if already running, or whether root authorization is needed for a destructive, non-idempotent mutation.

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-loaded, which is good, but the second sentence is filler that repeats the tool family's purpose without informing the call. Half the text earns no place.

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?

For a destructive, non-idempotent mutation with zero output schema, the description should say more about effects and failure modes. With only two well-documented parameters the gaps are limited, but an agent still cannot tell from the description what happens to a running service or how to interpret success.

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%, with both "service_name" and the "confirm" override documented in the schema itself. The description adds no meaning beyond that, so the baseline of 3 applies.

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?

The description states a clear verb+resource combination ("Start service"), so an agent knows the general action. However, the parenthetical "(sm_service_operations)" appears to be a grouping label rather than a scope statement, and nothing distinguishes this from siblings like manage_service_start or sm_service_restart_service, which a caller must choose between.

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 use this tool versus the numerous sibling service tools, and no mention of prerequisites such as the service being stopped first or requiring elevated privileges. The second sentence, "Operations for managing system services," is a category restatement rather than usage guidance.

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