Skip to main content
Glama

List security cluster posture

list_security_cluster_posture
Read-only

Per-cluster security posture across the fleet: each cluster's finding counts by severity, known-exploited count, scanner coverage and freshness, and its Kubernetes access posture summary (access_posture: live grants, standing elevated grants, grants over the access policy, grants verified able to impersonate). In access_posture a null over_policy or impersonate_reachable means Ankra could not establish that count (the access policy was unreadable, or not every grant has a verified impersonation probe), never 0, so report it as unverified rather than clean. Use to find the clusters driving the organisation's exposure. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
sortNoSort column.
orderNoasc or desc.
searchNoFilter clusters by name.
statusNoFilter by scanner status.
page_sizeNoResults per page (default 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses a genuinely non-obvious semantic: null over_policy or impersonate_reachable means the count could not be established and must be reported as unverified, never as 0/clean. That is exactly the kind of interpretation rule an agent could not derive from structured fields, and it prevents a dangerous misreading of the response. The "Read-only" restatement is redundant with the annotation but harmless.

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 response shape is front-loaded before the access_posture caveat and the use case, which is the right order for an agent deciding whether to call it. The parenthetical enumeration of access_posture fields is dense, and "Read-only" duplicates the annotation, but nothing is meaningfully wasted.

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 carries the full burden of explaining return values, and it does so field-by-field, including the null semantics that govern interpretation. Pagination and sorting are covered by the well-documented schema, so nothing needed to call or read this tool correctly 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 all six parameters (page, sort, order, search, status, page_size) are documented in the schema itself. The description adds no parameter-level meaning, such as what fields `sort` accepts or what values `status` takes, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and scope (per-cluster security posture across the fleet) and enumerates exactly what each row contains: finding counts by severity, known-exploited count, scanner coverage/freshness, and an access_posture summary. An agent can tell this is a fleet-wide rollup rather than a single-cluster or single-finding tool, though it never names the sibling tools (e.g. get_security_overview, list_clusters, list_cluster_security_stacks) it should be preferred over.

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?

"Use to find the clusters driving the organisation's exposure" gives a clear positive use case that maps to an exposure-triage workflow. There are no explicit exclusions, prerequisites, or named alternatives, so the agent must infer when to reach for a narrower per-cluster tool instead.

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.