Skip to main content
Glama

BRAINIAC Software Supply Chain Security

Match SBOM vulnerabilities

software-security_sbom-vulnerability-match
Read-onlyIdempotent

Parse a CycloneDX or SPDX SBOM, or a component list, and classify each exact package version against OSV advisories as affected, unaffected, or unknown. A similar package name is not a match. Price $0.08 USDC. POST /api/v1/software-security/sbom-vulnerability-match. An unpaid call returns the x402 payment terms and does not run.

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": "software-security_sbom-vulnerability-match"
  }
}

Input Schema

NameRequiredDescriptionDefault
sbomNosbom, string, length 2 to 400000. Optional.
componentsNocomponents, array. Optional.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
warningsNowarnings. Array.
componentsNocomponents. Array.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
approvesReleaseNoapprovesRelease. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new operational context: a $0.08 USDC price, the POST path, and the failure mode that an unpaid call returns x402 payment terms and does not execute. It does not cover rate limits or what happens when both input fields are supplied.

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?

Four short sentences, front-loaded with the core behavior, then the matching caveat, then the payment and endpoint facts. Nothing is repeated and no sentence is filler.

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

Completeness4/5

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

Return shape is covered by the output schema and safety by annotations, so the description only needed to add payment behavior, input formats, and match semantics — all present. The one unresolved gap is that no parameter is required, so the description should state what happens if the caller supplies neither sbom nor components.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description earns a bump by naming accepted formats (CycloneDX, SPDX) and clarifying that a component list is a legitimate alternative to a full SBOM, which maps to the two top-level properties. The nested component fields (purl, ecosystem, version) are left to the schema.

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 opens with a concrete verb (parse) and resource (CycloneDX/SPDX SBOM or component list) and names the exact output semantics: each exact package version classified against OSV advisories as affected, unaffected, or unknown. That framing implicitly separates it from siblings like kev-exposure-check or malicious-dependency-check, though it 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 Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for scanning an SBOM or component list for known vulnerabilities. There is no explicit when-to-use/when-not, no statement about which sibling to pick for KEV exposure versus malicious packages, and no guidance on choosing between the sbom and components input paths.

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