Skip to main content
Glama

Get cluster pod security

get_cluster_pod_security
Read-only

Read one pod's security container by container: for every app and init container the image, whether the scanner covered it, the actionable CVEs by severity, known-exploited count, fixable-severe count, and whether a bill of materials is stored (with component count and OS). Read-only. Use get_security_sbom_image / list_security_sbom_image_findings with a container's image_identity for the image's components and CVEs.

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>",
      "namespace": "<namespace>",
      "pod_name": "<pod_name>"
    },
    "name": "get_cluster_pod_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
pod_nameYesThe pod's name.
namespaceYesThe pod's namespace.
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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces it with 'Read-only.' while adding real behavioral context beyond the annotation: the result is per-container (app and init), and each container reports scan coverage plus BOM presence. It omits what happens when the pod is absent or the scanner did not cover an image, which is the main remaining gap for a read tool already covered by annotations.

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 the verb and scope, then a compact enumeration of returned fields, then the routing hint. The per-field enumeration is long but each item earns its place by telling the agent what it will get; only slight tightening is possible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 return-shape burden and does so thoroughly, listing every reported field per container. Missing are failure modes (pod not found, no scan coverage) and any hint that the pod's namespace must be in security scope, which would fully close the loop for a read tool.

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 three parameters (pod_name, namespace, cluster_id) are documented in-schema, including the list_security_cluster_posture hint for cluster_id. The description adds no parameter-level meaning; its mention of image_identity refers to output data, not an input. 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 ('Read one pod's security') plus a precise scope ('container by container', covering app and init containers) and enumerates exactly what comes back: image, scan coverage, CVEs by severity, known-exploited and fixable-severe counts, BOM presence with component count and OS. That level of detail makes it distinguishable from sibling pod and SBOM tools without opening a schema.

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 the agent to the alternative path: use get_security_sbom_image / list_security_sbom_image_findings with a container's image_identity for image-level components and CVEs. It does not, however, say when to prefer this over list_security_pods or list_security_workloads, nor mention prerequisites such as the namespace being security-enabled.

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.