Skip to main content
Glama
shyshlakov

pci-dss-mcp

generate_sbom

Create a CycloneDX v1.6 SBOM for Go projects. Parses go.mod and go.sum offline to build a software inventory, fulfilling PCI DSS 6.3.2 requirements.

Instructions

Generate a CycloneDX v1.6 SBOM for a Go project. Default behavior: writes sbom.json (or sbom.xml when format=xml) next to the scanned go.mod and returns metadata only (output_path, size_bytes, component_count, unknown_licenses). Override the destination with output_path (must be absolute). Pass inline=true to return the serialized SBOM in the MCP response instead (capped at 64 KB; returns SBOM_TOO_LARGE above that). Parses go.mod + go.sum offline against the local GOMODCACHE; cache-miss modules surface as UNKNOWN-LICENSE. Satisfies PCI DSS 6.3.2 (software inventory, mandatory since March 2025).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesrequired,Absolute path to the Go project directory containing go.mod (and go.sum)
formatNoOutput format: json (default) or xml
output_pathNoAbsolute path where the SBOM file should be written. Default: {path}/sbom.json or {path}/sbom.xml. Ignored when inline=true.
inlineNoIf true, return serialized SBOM inline in the response (64 KB cap, SBOM_TOO_LARGE on overflow). Default: false, write to file and return metadata only.
fixed_serialNoOverride generated serialNumber. Accepts bare UUID v4 or urn:uuid: form. Use for VEX linking and audit pipeline reproducibility.
no_timestampNoIf true, omit metadata.timestamp for reproducible builds.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
bom_formatYes
spec_versionYes
component_countYes
unknown_licensesNo
formatYes
generated_atYesRFC3339 UTC
project_pathYesAbsolute scanned path
output_pathNo
size_bytesNo
serialized_bomNo
fixed_serialNoOverride generated serialNumber (urn:uuid: or bare 36-char form)
no_timestampNoOmit metadata.timestamp for reproducible builds
Behavior5/5

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

Despite no annotations, description fully discloses behaviors: default file write, inline option with 64KB cap, cache-miss handling, compliance standard. No contradictions.

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?

Efficiently packed with information in a logical order (purpose, defaults, overrides, inline behavior, edge cases, compliance). Every sentence adds value.

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?

Given no annotations and complex functionality, description covers all key aspects: input, output, behavior, limitations, compliance. No gaps for an AI agent to misunderstand.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds significant meaning: default output path, inline size cap, UUID override, timestamp omission. Adds value beyond schema.

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?

Clearly states it generates a CycloneDX v1.6 SBOM for a Go project, with specific version and project type. Differentiates from sibling tools (other compliance/security tools) by focusing on SBOM generation.

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?

Provides clear context for use (PCI DSS compliance, software inventory) and explains default behavior. Lacks explicit alternatives or when-not-to-use scenarios, but context is strong.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shyshlakov/pci-dss-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server