Skip to main content
Glama

List security SBOM images

list_security_sbom_images
Read-only

List the container images that publish a bill of materials, with their base OS, component count, where they run and the findings currently attributed to them. Read-only. Use it to find an image's identity before calling get_security_sbom_image. The response's coverage block says how many scanned clusters publish an SBOM at all - clusters with SBOM generation switched off are absent from this list, not empty.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
sortNoSort column.
orderNoasc or desc.
searchNoMatch image reference, repository or registry.
namespaceNoOnly images running in this namespace.
page_sizeNoResults per page (default 50).
cluster_idNoOnly images running on this cluster (UUID).
workload_kindNoOnly images running in workloads of this kind (Deployment, StatefulSet, DaemonSet, CronJob, ...); case-insensitive.
workload_nameNoOnly images running in the workload with this name; case-insensitive. Combine with workload_kind to pin one workload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes the safe-read behavior, so the description's 'Read-only' sentence is somewhat redundant. However, it adds valuable behavioral context by explaining the coverage block and warning that clusters without SBOM generation are omitted rather than shown as empty.

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?

The description is front-loaded with the main purpose and returned fields, then follows with usage and a coverage caveat. It is generally efficient, though the explicit 'Read-only' sentence duplicates an annotation and could be removed without losing information.

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?

With no output schema, the description usefully summarizes what the list returns and explains the coverage block's meaning. Combined with the fully documented nine-parameter schema and the read-only annotation, it gives an agent enough information to invoke and interpret the tool 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 description coverage is 100%, and every parameter is already documented in the input schema, including page, sort, search, namespace, cluster_id, workload_kind, and workload_name. The description does not add further meaning about parameter interactions or formats beyond what the schema provides, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: it lists container images that publish an SBOM, and it names the returned content such as base OS, component count, runtime location, and attributed findings. It also distinguishes this image-level list from the downstream get_security_sbom_image lookup, so an agent can identify the right tool.

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 explicitly says to use this list to find an image's identity before calling get_security_sbom_image, giving a clear usage context. It also warns that clusters with SBOM generation disabled are absent rather than empty, which helps interpretation, though it does not compare against other related list tools such as list_security_sbom_containers or list_security_sbom_components.

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.