Skip to main content
Glama

List security pods

list_security_pods
Read-only

List the running pods of one namespace on one cluster with their containers and the findings the scanner attributes to each container: image, scanned or not (an unscanned container is not a clean one), actionable counts by severity, known-exploited and fixable-severe. Read-only. Narrow to one workload with workload_kind + workload_name or workload_uid. The listing is capped; capped=true says so.

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_pods"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
namespaceNoNamespace to list. Omit for every namespace of the cluster.
page_sizeNoResults per page (default 50).
cluster_idNoCluster id (UUID). Optional when the conversation is bound to a cluster.
workload_uidNoRestrict to the pods owned by this workload uid.
workload_kindNoOwner kind (Deployment, StatefulSet, DaemonSet, Job, CronJob) - pair with workload_name.
workload_nameNoOwner name - pair with workload_kind.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already carry readOnlyHint=true, so the 'Read-only' sentence adds nothing, but the description goes further with two genuinely new behaviors: results are capped and signalled via capped=true, and an unscanned container must not be read as clean. Those are interpretive caveats an agent cannot get from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads what is returned, then the read-only nature, then narrowing, then the cap caveat. Every sentence carries non-redundant information; the 'unscanned is not clean' aside is a deliberate warning rather than filler.

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?

For a 7-parameter, no-output-schema list tool, the description covers return shape, scoping and a truncation signal, which is what an agent needs to call it and interpret results. It omits pagination behavior and any statement about what an empty or fully unscanned namespace yields, which keeps it short of a 5.

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%, so the baseline is 3. The description adds the alternative framing that workload_uid or the workload_kind + workload_name pair narrows to one workload, and that namespace and cluster scope the listing — relationship information the per-parameter schema text does not state as a choice.

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?

States a specific verb and resource ('List the running pods of one namespace on one cluster') and enumerates the payload that distinguishes it from a plain pod listing: per-container image, scanned status, severity counts, known-exploited and fixable-severe. It separates itself implicitly from generic pod/security siblings by the per-container finding envelope, though it never names a specific alternative tool.

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

Usage Guidelines3/5

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

Offers scoping guidance ('Narrow to one workload with workload_kind + workload_name or workload_uid') but that is parameter usage, not when-to-use. There is no statement of when this is preferable to list_security_workloads, list_security_findings, or get_pods, and no exclusions.

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.