Skip to main content
Glama
Systems Manager

Systems Manager

Reboot

sm_system_reboot
Destructive

Reboots a managed system to apply updates or restore normal operation; set confirm=true when the client cannot answer an approval prompt.

Instructions

Reboot (sm_system_operations). System operations for managing packages, system health, and updates

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_system_reboot"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already flag destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is known. The description adds nothing beyond them — no warning about downtime, dropped connections, interrupted work, or whether the client must reconnect afterwards, which is the key behavioral context for a destructive reboot.

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, but the second sentence is filler about the tool group rather than the tool, and the one sentence that matters omits the critical information. Brevity here comes at the cost of substance rather than from efficiency.

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 operation with no output schema and zero annotation of side effects, the description should explain impact and recovery. It instead says nothing an agent couldn't already infer from the name and annotations.

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 the single 'confirm' parameter is fully documented in the schema itself. The description adds no meaning beyond that, so the baseline score 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 verb 'Reboot' is specific, but the target is never stated — nothing says whether it reboots the host, a service, or a container. The second sentence ('System operations for managing packages, system health, and updates') describes the sm_system_operations family rather than this tool, so it does nothing to distinguish reboot from siblings like sm_system_clean or sm_system_update.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance at all. Given siblings such as sm_system_update, sm_system_optimize, and sm_system_system_health_check, an agent has no basis from the text for choosing reboot over those alternatives.

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