Get bastion health
get_bastion_healthReport the SSH bastion health verdict the platform has already recorded for an Ankra-provisioned cluster: state (healthy, offline or unknown), which hop the probe failed at (bastion or jumphost), the failure detail, how many probe passes have failed in a row, the provider's own view of the VM when SSH failed, and when the bastion was last probed. This is a plain database read of what the bastion_health maintenance loop last saw - it answers immediately and never touches the host, so use it, not diagnose_bastion, to answer "is the bastion up?". Reach for diagnose_bastion only when the host itself must be inspected over SSH (sshd configuration, failed logins, disk, journal), and only when this tool reports diagnose_supported true - some bastions are probed but have no diagnosis lane (Scaleway's managed Public Gateway). An empty state and checked_at mean the bastion has not been probed yet. Clusters reached through their agent rather than a bastion - imported and managed-Kubernetes clusters - have no bastion to report on.
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": {
"cluster_id": "<cluster_id>"
},
"name": "get_bastion_health"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cluster_id | Yes | Ankra cluster id (UUID) the call targets. Discover ids with list_clusters. |