Skip to main content
Glama

Diagnose bastion

diagnose_bastion
Read-only

Inspect the SSH bastion host of an Ankra-provisioned cluster: sshd configuration, failed-login volume and top sources over the last 24 hours, disk usage, failed systemd units, recent journal errors, listening ports and pending security updates. Read-only. Use this after a bastion outage, or when asked about the bastion's security posture - the bastion runs no kubelet, so ssh_diagnose_node cannot inspect it. It reaches the host over SSH rather than through the cluster agent, because the agent sits behind the bastion. It cannot succeed while the bastion is offline - call get_bastion_health first, which answers the platform's recorded verdict without touching the host. For the power action, restart_node with target="bastion" reboots the bastion VM.

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

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
Behavior4/5

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

Annotations only supply readOnlyHint=true, and the description adds real behavioral context beyond that: the call reaches the host over SSH rather than through the cluster agent (which sits behind the bastion), and it cannot succeed while the bastion is offline. What is missing is any indication of latency, permission/SSH-key requirements, or failure output for an unreachable host.

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?

Content is front-loaded: the inspection scope comes first, then routing, then preconditions and the power-action alternative. It is long but nearly every sentence carries routing or precondition value; the SSH-vs-agent rationale is the one clause that could be tightened.

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 read-only diagnostic with one required parameter and no output schema, the description covers what is collected, how it connects, when it will fail, what to call first, and which sibling handles node-level or power actions. An agent has everything needed to select and invoke it correctly.

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?

There is a single parameter and schema description coverage is 100% — the schema already explains that cluster_id is an Ankra UUID discoverable via list_clusters. The description adds no further semantics about the parameter, so 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?

Names a specific verb (Inspect) and resource (SSH bastion host of an Ankra-provisioned cluster), then enumerates exactly what is collected: sshd config, failed-login volume and sources, disk usage, failed systemd units, journal errors, listening ports, pending security updates. It explicitly differentiates from the sibling ssh_diagnose_node by explaining the bastion runs no kubelet.

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 triggering conditions ('after a bastion outage, or when asked about the bastion's security posture') and names the alternative for the node case (ssh_diagnose_node). It also adds a prerequisite gate — call get_bastion_health first when the host may be offline — and routes the power action to restart_node with target="bastion".

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.