Skip to main content
Glama

List security SBOM containers

list_security_sbom_containers
Read-only

List every container the resource cache says is running on the scoped clusters, init containers included, each joined to the bill of materials of its image or marked absent when the scanner has none for it. This is the tool for "which running containers have no bill of materials" and "what does this workload actually run": absent rows are listed, sorted first, and counted in the inventory block, because a missing bill of materials is a state to act on (SBOM generation off on the cluster, a registry the scanner cannot pull from, a tag rolled since the last scan) - never proof the image is empty. Filter by cluster, namespace, workload (kind and/or name; a bare pod matches its own name) and status. 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_sbom_containers"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
sortNoSort column: status (absent first), image, container, pod, namespace, workload, cluster_name, components, last_seen_at.
orderNoasc or desc.
searchNoMatch image, container, pod, workload or namespace.
statusNopresent (image has a bill of materials), absent (it does not) or any.
namespaceNoOnly containers in this namespace.
page_sizeNoResults per page (default 50).
cluster_idNoOne cluster (UUID); omit for every live cluster of the organisation.
workload_kindNoMatch the resolved workload, its direct owner, or 'pod' for bare pods; case-insensitive.
workload_nameNoMatch the resolved workload, its direct owner, or the pod name; case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, and the description confirms "Read-only" while adding behavior well beyond that: absent rows are sorted first and counted in the inventory block, and absence is explained as an actionable state (SBOM generation off, unpullable registry, tag rolled) rather than proof the image is empty. That interpretive guidance is exactly the kind of context an agent cannot get from the annotation or schema.

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?

It is front-loaded with what is listed and what is joined, then the use cases, then the interpretation caveat, then filters. Every sentence carries content, though the dense em-dash cascade in the absence sentence makes it slightly heavier than necessary for a read-only list tool.

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?

For a 10-parameter, all-optional read-only listing tool with no output schema, the description covers scope, row ordering, an inventory count, how to interpret the key edge case, and the available filter dimensions. Nothing an agent needs in order to call it correctly or read its output is missing.

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 schema carries the bulk of parameter documentation and the baseline would be 3. The description still adds meaning: it frames the filterable dimensions as a set, clarifies that a bare pod matches its own name for workload filters, and explains the absent/present status semantics in operational terms, which the schema only labels.

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?

The description opens with a specific verb and resource ("List every container ... running on the scoped clusters") and immediately narrows scope: init containers included, each joined to its image's bill of materials or marked absent. That combination of verb, resource, and join semantics clearly separates it from siblings like list_security_sbom_images or list_security_pods.

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?

It gives explicit triggering questions ("which running containers have no bill of materials", "what does this workload actually run") plus a usable filter set: cluster, namespace, workload kind/name (with the bare-pod rule) and status. It stops short of naming a sibling tool to use instead or stating when not to use it, so it is strong context without full alternative routing.

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.