Skip to main content
Glama

SSH repair node

ssh_repair_node
Destructive

Repair one Kubernetes node of an Ankra-provisioned cluster (Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, AWS, or Ankra Cloud) at the OS level over SSH-via-bastion: restarts the node's Kubernetes service unit (k3s / k3s-agent / kubelet) wrapped in Ankra's node-recovery engine, which classifies the failure and applies the matched curated fix (clear a failed unit, extend a start timeout, kill stale listeners, unblock the apiserver firewall, re-bootstrap the kubelet), verifies, and retries once. This is a privileged, not-cleanly-reversible action on a production node and briefly disrupts its workloads, so it requires confirmation. It does NOT run arbitrary commands - only the curated recovery plan. Always call ssh_diagnose_node first to confirm the node is broken at the OS level (not merely unreachable via bastion, which a node reboot - restart_node - addresses instead). Identify the node with node_id (preferred) or node_name. Not available for imported or managed-Kubernetes clusters, nor (yet) Proxmox/HPE Morpheus.

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

Input Schema

NameRequiredDescriptionDefault
node_idNoUUID of the node to repair. Preferred when known (from list_cluster_nodes).
node_nameNoExact name of the node to repair. 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.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds substantial context beyond them: it is 'privileged, not-cleanly-reversible', 'briefly disrupts its workloads', and 'requires confirmation'. It also bounds the action ('does NOT run arbitrary commands - only the curated recovery plan'), enumerates the curated fixes, and discloses a single retry. What it omits is the observable outcome/verification detail, which keeps it off a 5.

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?

The action and its risk are front-loaded in the first sentence, and nearly every clause carries information (mechanism, risk, prerequisite, exclusions). It is a single dense paragraph with heavy parentheticals, though, and the alternative-tool routing sits at the end where it would read better earlier.

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

Completeness5/5

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

For a privileged, zero-required-param repair tool with no output schema, the definition covers everything an agent needs: prerequisite diagnosis, risk and confirmation requirement, scope of the fix, one retry, node identification, and unsupported cluster/provider types. Nothing material is missing.

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 schema already marks node_id as 'Preferred when known' and node_name as the alternative, so the description's 'Identify the node with node_id (preferred) or node_name' largely restates structured data. It adds nothing about cluster_id/cluster_name resolution beyond what the schema says. Baseline 3 is appropriate.

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 ('Repair one Kubernetes node ... at the OS level over SSH-via-bastion') and immediately explains the mechanism: it restarts the k3s/k3s-agent/kubelet unit wrapped in the node-recovery engine with curated fixes. It is clearly distinguishable from near-siblings: ssh_diagnose_node (confirm the break first) and restart_node (for bastion-unreachable nodes). The supported provider list further pins down scope.

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?

Gives explicit preconditions ('Always call ssh_diagnose_node first to confirm the node is broken at the OS level'), an explicit when-not ('not merely unreachable via bastion, which a node reboot - restart_node - addresses instead'), and hard exclusions ('Not available for imported or managed-Kubernetes clusters, nor (yet) Proxmox/HPE Morpheus'). No alternatives are left to inference.

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.