Skip to main content
Glama

Get bastion health

get_bastion_health
Read-only

Report 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

NameRequiredDescriptionDefault
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered before the description is read. The description still adds real behavioral context: it is a plain database read, answers immediately and never touches the host, an empty state/checked_at means never probed, and some bastions (Scaleway managed Public Gateway) are probed but have no diagnosis lane. These are genuine disclosures beyond the annotation, though pagination/latency details remain unstated.

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?

Front-loaded with the returned fields before the routing advice, and nearly every sentence earns its place. It is one long run-on clause chain, so the enumerate-then-route structure is denser to scan than it needs to be, and diagnose_bastion guidance is restated twice.

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?

There is no output schema, so the description carries the return-value burden and does so fully by naming each reported field and its meaning, including the empty-state sentinel. Combined with the routing rules and the no-bastion exclusion, an agent has everything needed to call it and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single cluster_id parameter, so the baseline is 3. The description adds scope meaning the schema cannot: which clusters this parameter is even valid for (agent-reached imported and managed-Kubernetes clusters have no bastion to report), which prevents a wasted or misread call.

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 ('Report the SSH bastion health verdict... recorded for an Ankra-provisioned cluster') and enumerates the exact fields returned (state, failing hop, failure detail, consecutive failures, provider VM view, last probe time). It explicitly distinguishes itself from diagnose_bastion, the closest sibling, so an agent can pick between them without opening schemas.

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 when-to-use ('use it, not diagnose_bastion, to answer "is the bastion up?"'), when-not ('Reach for diagnose_bastion only when the host itself must be inspected over SSH'), and a precondition gate ('only when this tool reports diagnose_supported true'), plus the edge case that imported/managed-Kubernetes clusters have no bastion at all.

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.