Skip to main content
Glama

Restart node

restart_node
Destructive

Restart one provisioned VM node of an Ankra-managed cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, Ankra Cloud, or Proxmox) - a control-plane node, a worker, or the cluster's bastion/gateway. Schedules a native reboot (falling back to a power cycle) through the cloud provider API as a tracked operation; the node must be in the 'up' state and have no restart already in flight. Workloads on the node are briefly unavailable while it reboots. This is the fix for a VM that is hung or powered off - the case where SSH cannot reach the node at all. It is not a remedy for failed addon/manifest deploys or an unresponsive cluster agent, which ride the agent's outbound message-bus connection rather than node SSH. Identify the node with node_id (preferred, from list_cluster_nodes), node_name (exact match), or target="bastion" (the cluster's singleton bastion/gateway, no name needed). Always call list_cluster_nodes first if you do not already have the node_id. Not supported for HPE Morpheus or non-Ankra-provisioned clusters.

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

Input Schema

NameRequiredDescriptionDefault
targetNoConvenience selector for the cluster's singleton bastion/gateway node, when you don't know its name.
node_idNoUUID of the node to restart. Preferred when known (from list_cluster_nodes).
node_nameNoExact name of the node to restart. Alternative to node_id.
cluster_idNoUUID of the cluster the node belongs to. Optional when a cluster is selected.
cluster_nameNoExact name of the cluster the node belongs to. Optional when a cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark this destructive, non-idempotent, and non-read-only, but the description still adds real substance: the reboot is scheduled via the cloud provider API with a power-cycle fallback, it is a tracked operation, workloads are briefly unavailable during reboot, and HPE Morpheus or non-Ankra-provisioned clusters are unsupported. Those are exactly the facts an agent needs before calling a destructive mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then behavior and side effects, then exclusions, then node identification and prerequisites. The sentences are dense but every one carries decision-relevant information; the SSH contrast earns its place by making the exclusions concrete.

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, no-output-schema mutation this covers preconditions, blast radius, platform support, and node identification thoroughly. The only gap is that it calls the restart a 'tracked operation' without saying how an agent observes completion or recovery.

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%, so the baseline is 3, and the description mostly restates it (node_id preferred from list_cluster_nodes, node_name exact match, target="bastion" for the singleton). It does add useful selection ordering, but it names only the bastion value while the schema enum also allows "gateway", so it adds no coverage the schema lacks.

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 and resource (restart one provisioned VM node), enumerates supported providers, and names the node roles covered (control-plane, worker, bastion/gateway). It is clearly distinguishable from siblings like ssh_diagnose_node and ssh_repair_node because it describes the action taken (native reboot, then power cycle) rather than a diagnostic path.

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

Usage Guidelines5/5

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

Explicit when-to-use (a VM that is hung or powered off, where SSH cannot reach the node at all) and explicit when-not-to-use (failed addon/manifest deploys, unresponsive cluster agent that rides the outbound message bus). It also gives preconditions (node in 'up' state, no restart in flight) and a sequencing instruction to call list_cluster_nodes first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.