Skip to main content
Glama

List cluster security stacks

list_cluster_security_stacks
Read-only

List every stack of one cluster with its security posture - the way Ankra deployed the cluster: per stack the status (connected, stale, no_reports, unmatched, unscanned, empty), how many add-ons and manifests it has and how many workloads they resolved to, the observed and actionable CVE counts by severity, known-exploited (CISA KEV) and fixable-severe counts, and the running containers with and without a bill of materials. Also returns outside: everything on the cluster no stack owns (system namespaces, node images), so the rows add up to the cluster. Read-only. Start here for 'which stack should we fix first' and drill with get_cluster_stack_security.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idYesThe cluster id (uuid). list_security_cluster_posture lists the 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 declare readOnlyHint=true, so the description carries most of the behavioral burden and does so: it discloses the full status vocabulary (connected, stale, no_reports, unmatched, unscanned, empty) and the existence of an 'outside' bucket (system namespaces, node images) so the caller understands the rows reconcile to the whole cluster. It does not mention pagination, row limits, or cost of the call, which keeps it short of a 5.

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 verb and resource, then a dense enumeration of return fields and a closing usage sentence. It is long but nearly every clause adds distinct information; the only redundancy is the 'Read-only.' sentence, which repeats the readOnlyHint annotation.

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 must explain the return shape, and it does: status categories, counts, CVE breakdown, container/BOM data, and the 'outside' remainder. For a single-parameter read tool this is complete enough to invoke and interpret 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?

Schema coverage is 100% and the schema description already explains cluster_id as a uuid and points to list_security_cluster_posture for discovery. The description adds no further parameter meaning, 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?

Opens with a specific verb and resource ('List every stack of one cluster with its security posture') and then enumerates exactly what each row carries: status values, add-on/manifest counts, resolved workloads, CVE counts by severity, KEV and fixable-severe counts, and BOM coverage. That is far more specific than the title and cannot be confused with siblings like list_stacks or get_cluster_security_report_schedule.

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?

Explicitly routes the agent: 'Start here for which stack should we fix first and drill with get_cluster_stack_security.' It names the follow-up tool and the condition that selects it, which is exactly the when-to-use guidance the dimension asks for.

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.