Skip to main content
Glama

Get cluster baseline

get_cluster_baseline
Read-only

Get a cluster's Ankra Baseline score: the latest nightly evaluation of ten checks (metrics and logs collected, service-level alerts, backups with a tested restore, resource requests and limits, readiness and liveness probes, PodDisruptionBudgets on multi-replica workloads, pinned images, supported Kubernetes and addon versions, certificate automation, no critical or known-exploited CVEs), each pass, fail or unknown with the evidence it rests on. The score is passed weight over decided weight; unknown checks leave the denominator and are reported as coverage, never as a pass. Call this when the user asks how well a cluster is built, what to fix first, whether it is production-ready, or for a hardening or prevention plan: the gaps are ordered heaviest first. Read from the platform database (works for offline clusters); 'computed' false means the nightly recorder has not scored the cluster yet, which is not a score of zero.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the cluster to score. Optional when a cluster is selected.
cluster_nameNoExact name of the cluster to score. Optional when a cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnlyHint=true, it discloses the data source (platform database, so offline clusters work), the meaning of 'computed': false as 'not yet scored' rather than zero, and how unknowns are excluded from the denominator and surfaced as coverage. It also states that gaps are ordered heaviest first, which is real behavioral context an agent could not infer from annotations or schema.

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 purpose and the score formula are front-loaded, and each clause carries information (check list, formula, trigger conditions, offline/computed caveat). The ten-check enumeration inside a single long sentence makes it dense and slightly hard to scan, but nothing is redundant.

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?

With no output schema, the description still explains the return shape well enough to act on: per-check status with supporting evidence, an aggregate passed-over-decided score, coverage for unknowns, and gap ordering. The 'computed' caveat closes the main way an agent could misread the result as a zero score.

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%, so both cluster_id and cluster_name are already documented. The description adds no selector semantics of its own — it never says how the two selectors are resolved or what happens if both are supplied — so the baseline 3 applies.

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 ('Get a cluster's Ankra Baseline score') and then defines exactly what that score is: the latest nightly evaluation of ten named checks, each pass/fail/unknown with evidence. The concrete check list and the score formula make it unmistakable against siblings like get_cluster_pod_security or get_cluster_insights.

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

Usage Guidelines4/5

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

Gives explicit triggering conditions: user asks how well a cluster is built, what to fix first, whether it is production-ready, or wants a hardening/prevention plan. It does not name an alternative tool or a when-not-to-use case (e.g., versus get_cluster_insights or get_security_compliance_overview), which keeps it below a 5.

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.