Skip to main content
Glama

security-crypto

sbom_inspect_and_audit

Inspect CycloneDX or SPDX JSON Software Bill of Materials (SBOM) to count components, extract PURLs, and summarize license distribution.

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": "sbom_inspect_and_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden: it implies a read-only inspection but never says whether filePath reads from the local filesystem (a meaningful security/IO detail), how invalid JSON or unsupported spec versions are handled, or whether it truncates output for large SBOMs. Only the operation vocabulary hints at behavior.

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?

A single dense sentence that front-loads the resource and the accepted formats, with zero filler. It could be slightly better structured only if it split purpose from accepted inputs.

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?

For a two-parameter tool with no annotations and no output schema, listing the three returned summaries partially compensates by describing results. However, the input side (text vs filePath, validation expectations) is entirely absent, which is a real gap for an agent trying to call it correctly.

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

Parameters2/5

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

Two parameters at 0% schema description coverage, and the description says nothing about them. Critically, it never clarifies whether text and filePath are alternatives (either/or) or both accepted, nor what input format each expects, leaving an agent to guess at invocation.

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 (inspect) plus resource (CycloneDX/SPDX JSON SBOM) and enumerates the three concrete outputs: component counts, PURLs, and license distribution. That is enough to distinguish it from the license-compatibility sibling, though it does not name any sibling 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 when-to-use or when-not-to-use guidance, no mention of prerequisites (valid JSON, supported spec versions), and no routing to alternatives such as spdx_license_compatibility. The purpose implies usage but the definition never states conditions.

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.

Resources