Systems Manager

Sm Service Operations

sm_service_operations

Manage system services by listing them, checking status, and starting, stopping, restarting, enabling, or disabling services as needed.

Instructions

Operations for managing system services

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": {
      "action": "<action>"
    },
    "name": "sm_service_operations"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	Action to perform. Must be one of: 'list_services', 'get_service_status', 'start_service', 'stop_service', 'restart_service', 'enable_service', 'disable_service'
`confirm`	No	Explicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.
`service_name`	No	Name of the service

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.9Nov 3, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "description": "Explicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.",
+  "type": "boolean"
+}

First observedv2.2.5Oct 24, 2026

TDQS

C2.3/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It does not mention that several actions (start, stop, restart, enable, disable) are mutating, nor does it explain the confirm parameter, required privileges, or side effects of stopping or disabling a service.

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?

The description is a single short sentence with no wasted wording, but it is under-specified rather than concise. It is front-loaded but provides too little substance for a multi-action tool.

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 multi-action tool containing both read and mutating operations, with no annotations and no output schema. A one-sentence generic description leaves out action semantics, mutation risks, confirmation behavior, and service_name requirements, so it is not complete enough for safe invocation.

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 the schema already documents action, confirm, and service_name. The description adds no additional meaning beyond those structured fields, which fits the baseline 3 for high schema coverage.

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

Purpose2/5

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

The description says only 'Operations for managing system services', which restates the tool name and title without naming a specific operation or scope. With siblings like manage_service and list_services, an agent cannot tell from this sentence which service operations belong to this tool.

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 and no mention of alternatives such as manage_service or list_services. The agent must infer from the schema that this tool handles list/status/start/stop/restart/enable/disable actions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.