Skip to main content
Glama
Sign In
mia

mia

by akadorkin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

host_reboot

Reboots Linux hosts in rolling batches, waits for each to return over SSH with remnanode running, and requires a dry-run plan before applying changes.

Instructions

Reboot hosts (shutdown -r +delay) and wait for each to come back over ssh with remnanode running before the next one (rolling, batch 1). The dry run shows users online per node (panel) and whether a reboot is pending anyway.

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": "host_reboot"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNowait for the host to return (up to 10 min) before the next batch
applyNofalse (default) = dry run: show what will happen on which hosts and a planHash. true = run it; needs planHash
batchNohosts at a time (rolling). Default depends on the action: 1 for disruptive ones
targetNohosts: all | <host> | <glob nl-*> | <group> | role:<edge|remnanode|panel|docker> | tag:<tag>; comma-separated, !x excludesall
delayMinNo
planHashNoplanHash from the dry run of the very same call, good for one apply; refused if targets or their state changed since
continueOnErrorNokeep going after a host fails (default: stop the rollout at the first failure)
skipUnreachableNoskip hosts that do not answer over ssh instead of refusing the whole plan (they show as skipped)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description must carry the behavioral burden, and it discloses a lot: rolling batch-1 sequential reboots, waiting for ssh + remnanode to return before the next host, and that the dry run reports users online per node and pending-reboot state. It omits permission requirements and failure/recovery details beyond what parameters imply, so it is strong but not exhaustive.

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 dense sentences that are front-loaded with the core action and mechanism, with secondary dry-run detail trailing. Almost every clause carries information, though the phrasing is compressed enough to border on terse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, 8-parameter tool with no annotations and no output schema, the description supplies the operation mechanics and dry-run behavior needed to call it safely. It lacks explicit safety/permission framing and does not describe the return payload, but the pre-flight dry-run and planHash params largely cover the safety story.

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 88%, so the schema already documents nearly all parameters. The description only reinforces the dry-run visibility ('users online per node') and rolling batch behavior, adding little syntax or format detail beyond the schema's own descriptions of wait, apply, target, etc.

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

Purpose5/5

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

States a specific verb (Reboot) and resource (hosts) and immediately adds the mechanism (shutdown -r +delay) and rolling semantics. No sibling tool in the list performs a reboot, so the purpose is unambiguous and clearly differentiated.

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

Usage Guidelines3/5

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

The description implies a dry-run-then-apply workflow and mentions rolling batch behavior, which hints at how to use it. However it never states when to prefer this over alternatives (e.g., host_exec or service_action), nor prerequisites such as required access. Usage is implied rather than explicit.

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