Skip to main content
Glama

Get cluster stack security

get_cluster_stack_security
Read-only

Read one stack's full security posture on a cluster: status, scope, the CVE posture across its workloads, the CISA-listed exploited findings among them, the top actionable findings, the bill-of-materials picture, and the same figures per member (add-on or manifest). A member with zero matched workloads is unmatched, never clean. Read-only. Drill further with list_security_sbom_containers (a member's pods and containers, by workload_kind + workload_name) and get_cluster_pod_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>",
      "stack_name": "<stack_name>"
    },
    "name": "get_cluster_stack_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idYesThe cluster id (uuid). list_security_cluster_posture lists the clusters.
stack_nameYesThe stack's name as list_cluster_security_stacks lists it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so restating 'Read-only' adds little. The genuinely valuable addition is the interpretive rule that a member with zero matched workloads is 'unmatched, never clean', which prevents a serious misreading of results. Beyond that it does not disclose permissions, pagination, or latency characteristics, so it is useful but not rich relative to a substantial read tool.

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-loads the core action and the enumerated output facets, then closes with drill-down pointers and the unmatched caveat; every clause carries information. The output enumeration is long but each item is a distinct fact, so density is justified rather than padded.

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, and the description compensates by naming the return facets and the per-member breakdown, plus a critical edge-case semantic and two follow-on tools. For a two-parameter read tool, an agent has everything needed to call it and interpret results.

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% and both parameters carry descriptions pointing at the listing tools that supply valid values, so the baseline is 3. The description adds conceptual meaning by defining what a stack member is ('add-on or manifest') and that output is broken down per member, which helps the agent understand what stack_name scopes to.

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 ('Read one stack's full security posture on a cluster') and then enumerates the exact facets covered: status, scope, CVE posture, CISA-listed exploited findings, top actionable findings, BOM, and per-member figures. An agent can immediately separate this from siblings like get_cluster_addon_security or get_cluster_pod_security.

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?

Explicitly routes deeper investigation to list_security_sbom_containers (with workload_kind + workload_name) and get_cluster_pod_security, which is clear alternative guidance. It lacks an explicit 'when not to use this / use X instead' for the peer stack-level tools, so it stops just short of full routing guidance.

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.