Skip to main content
Glama

capture_sbom_evidence

Generates a CycloneDX v1.5 SBOM from workspace package manifests and lockfiles, then records verifiable supply-chain evidence on the target bundle.

Instructions

Generates a CycloneDX v1.5 SBOM from workspace package manifests/lockfiles and records verifiable supply-chain evidence on the bundle.

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": {
      "bundleId": "<bundleId>"
    },
    "name": "capture_sbom_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundleIdYesThe unique identifier of the evidence bundle.
outputPathNoOptional relative file path within the workspace to write the CycloneDX v1.5 JSON file.
workspaceNameNoOptional registered monorepo package name.
workspacePathNoOptional workspace path hint to locate the bundle.
includeDevDependenciesNoWhether to include development dependencies in the SBOM inventory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose meaningful behavior: the data source (package manifests/lockfiles), the output format (CycloneDX v1.5), and that it writes evidence onto a bundle, implying mutation. It omits what happens when manifests/lockfiles are absent, whether the recorded evidence is immutable or idempotent on re-run, and any permission requirements.

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?

A single front-loaded sentence where each clause earns its place: the verb, the exact format and version, the input source, and the side effect on the bundle. No filler or repetition of the tool name.

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?

All parameters are documented and no output schema exists, so the main gaps are behavioral: with no annotations and a mutating side effect on a bundle, the definition should say more about preconditions and the consequence of recording evidence. Adequate for basic invocation, thin for a mutation on evidence state.

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 all five parameters are already documented, giving a baseline of 3. The description adds only indirect meaning, tying workspaceName/workspacePath to manifest discovery and outputPath to the CycloneDX JSON artifact; it says nothing about includeDevDependencies beyond what the schema states.

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 (generates) and a specific resource with format and version (CycloneDX v1.5 SBOM), plus a second effect (records supply-chain evidence on the bundle). That clearly separates it from capture_ast_evidence and capture_git_evidence, whose resources differ, though the description never names an alternative explicitly.

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?

There is no explicit when-to-use, when-not-to-use, or prerequisite guidance. An agent can infer it is the SBOM-capture member of the capture_*_evidence family, but nothing says whether a bundle must exist first, or when to prefer this over snapshot_files or the other capture tools.

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