Skip to main content
Glama

generate_sbom

Generate a CycloneDX SBOM from package URLs or directory scans for software inventory, vulnerability tracking, and compliance documentation.

Instructions

Generate a Software Bill of Materials (SBOM) in CycloneDX format using purl2notices.

This tool creates comprehensive SBOMs in CycloneDX 1.4 JSON format for software inventory, vulnerability tracking, and compliance documentation.

SBOM includes: name, version, PURL, licenses, homepage (external references). Data is sourced from purl2notices scan mode which provides accurate package metadata.

Use this tool when:

  • You need to generate an SBOM for a project or package list

  • Creating inventory documentation for compliance

  • After analyzing packages and need structured output

  • Preparing documentation for security audits

  • Required by procurement or regulatory requirements

Input modes:

  • Provide purls (list of Package URLs) for packages you've already identified

  • Provide path to scan a directory and generate SBOM from discovered packages

  • At least one of purls or path must be provided

Args: purls: Optional list of Package URLs (PURLs) to include in SBOM path: Optional directory path to scan for packages output_file: Optional path to save the SBOM file (CycloneDX JSON format) include_licenses: If True, include license information (default: True)

Returns: Dictionary containing: - sbom: The generated SBOM structure (CycloneDX 1.4 JSON) - packages_count: Number of packages included - output_file: Path to saved file (if output_file was specified)

Examples: # Generate SBOM from PURLs (after batch analysis) generate_sbom( purls=["pkg:npm/express@4.0.0", "pkg:pypi/django@4.2.0"], output_file="/tmp/sbom.json" )

# Generate SBOM by scanning directory
generate_sbom(path="/path/to/project")

# After batch scan workflow
scan_result = check_package("package.jar")
generate_sbom(purls=[scan_result["purl"]], include_licenses=True)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNo
purlsNo
output_fileNo
include_licensesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes data sources (purl2notices scan mode), output format, and included fields. Discloses that at least one of purls or path is required. However, does not discuss potential side effects like overwriting an existing output file or behavior when both purls and path are provided.

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?

Well-structured with sections and examples, but somewhat verbose with repetition (e.g., CycloneDX mentioned multiple times). Could be tightened without losing clarity.

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 the existence of an output schema (not shown), the description need not detail return values, yet it still provides a structured dictionary summary. Covers input modes, optional parameters, and examples, making it fully adequate for agent selection and invocation.

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?

Despite 0% schema coverage, the description provides detailed parameter explanations in the 'Args' section and examples. Each parameter's purpose, type, and default are clearly explained, adding significant meaning beyond the raw 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?

Description clearly states it generates an SBOM in CycloneDX format. It distinguishes from sibling tools (e.g., scan_directory, check_package) which focus on scanning or checking packages, not generating structured SBOM output.

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?

Includes a 'Use this tool when:' section listing specific scenarios like compliance documentation and security audits. Lacks explicit exclusions or comparisons to alternative tools, but the scenarios are clear and relevant.

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/SemClone/mcp-semclone'

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