Skip to main content
Glama
Sign In
RAD Security

RAD Security

Official
by rad-security
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_image_sbom

Extract the Software Bill of Materials (SBOM) from a container image to identify components and dependencies for security analysis in Kubernetes environments.

Instructions

Get the SBOM of a container image

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": {
      "digest": "<digest>"
    },
    "name": "get_image_sbom"
  }
}

Input Schema

NameRequiredDescriptionDefault
digestYesImage digest (required for SBOM)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic function without disclosing behavioral traits like authentication needs, rate limits, or response format. It lacks details on what 'Get' entails operationally, such as whether it's a read-only fetch or has side effects.

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?

The description is a single, clear sentence with zero waste, front-loading the key information efficiently. It's appropriately sized for the tool's simplicity.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has one parameter with full schema coverage and no output schema, the description is minimally adequate but lacks context on behavioral aspects and usage guidelines. It's complete enough for basic understanding but misses details needed for optimal agent invocation.

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%, so the schema already documents the 'digest' parameter fully. The description adds no additional meaning beyond implying the digest is for SBOM retrieval, but doesn't clarify format or constraints beyond the schema, meeting the baseline for high coverage.

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?

The description clearly states the action ('Get') and resource ('SBOM of a container image'), making the purpose evident. However, it doesn't differentiate from sibling tools like 'get_container_details' or 'list_images', which might also involve container images, so it lacks sibling distinction.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, such as 'list_image_vulnerabilities' or other container-related tools. The description only states what it does, not when it's appropriate, leaving usage unclear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools