Skip to main content
Glama

BRAINIAC Application & Pipeline Security Checks

Generate an SBOM from a lockfile

appsec-config_sbom-generate
Read-onlyIdempotent

Build CycloneDX or SPDX SBOMs from npm/PyPI/Go/Cargo lockfiles. Price $0.03 USDC. POST /api/v1/appsec-config/sbom-generate. An unpaid call returns the x402 payment terms and does not run.

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": {
      "lockfile": "<lockfile>"
    },
    "name": "appsec-config_sbom-generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoformat, string, one of cyclonedx-1.6-json, spdx-2.3-json. Required.cyclonedx-1.6-json
lockfileYeslockfile, object. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
metadataNometadata. Object.
bomFormatNobomFormat. String.
componentsNocomponents. Array.
limitationsNolimitations. Array.
specVersionNospecVersion. String.
dependenciesNodependencies. Array.
serialNumberNoserialNumber. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world. The description adds genuinely new behavior: a $0.03 USDC charge and the fact that an unpaid call returns x402 payment terms instead of executing, which an agent must know before calling. It stops short of mentioning size limits or failure modes for malformed lockfiles.

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?

Three short sentences with zero padding: capability first, then cost, then endpoint, then the payment-gate consequence. Front-loading and ordering are exactly what an agent needs.

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?

An output schema exists, so return shape need not be described; the description instead covers the non-obvious operational facts (price, payment gate, endpoint) for a 2-parameter read-only tool. Nothing an agent needs to invoke it correctly is missing at this complexity level.

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 is 3, but the description adds real meaning by mapping ecosystems (npm/PyPI/Go/Cargo) onto the lockfile `type` enum values such as package-lock, requirements, go-mod and cargo-lock. It says nothing extra about `format` beyond the enum wording.

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?

States a specific verb and resource ('Build CycloneDX or SPDX SBOMs') plus the accepted input ecosystems (npm/PyPI/Go/Cargo lockfiles). No sibling tool in the list produces SBOMs, so the agent can distinguish it from the audit-family tools without opening the schema.

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?

The description implies when the tool applies (you have a lockfile) and discloses the payment precondition, but it never states when to choose this versus another tool or what inputs are out of scope. Usage is inferable rather than prescribed.

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