Skip to main content
Glama

BRAINIAC Software Supply Chain Security

Report dependency risk

software-security_dependency-risk-report
Read-onlyIdempotent

Summarise affected, unaffected, and unknown OSV advisory counts for each exact dependency version. No risk score is calculated. Price $0.08 USDC. POST /api/v1/software-security/dependency-risk-report. 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_dependency-risk-report"
  }
}

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.7/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, but the description adds operationally important facts they cannot: a $0.08 USDC price, the x402 payment flow, and the failure mode where an unpaid call returns payment terms instead of running. It does not describe response contents, though an output schema exists to cover that.

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?

Four short sentences, front-loaded with the behavioral scope before cost and transport details. The literal endpoint path is arguably noise for an agent, but everything else earns its place.

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?

For a two-parameter read-only report with a full output schema, the description covers purpose, cost, payment gating and the no-risk-score caveat. The remaining gap is guidance on choosing this tool over the sibling vulnerability and malicious-dependency checks.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents both sbom and components. The description only echoes the concept of an 'exact dependency version', adding no detail on how sbom and components interact or which takes precedence, so the baseline 3 applies.

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 first sentence gives a specific verb (summarise) and resource (OSV advisory counts per exact dependency version), and the note that no risk score is calculated separates it from scoring-style siblings. It stops short of naming which sibling to use for scoring or SBOM matching, so differentiation is by scope rather than by explicit routing.

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 per-version advisory count report and not a risk-scoring tool. There is no explicit statement of when to prefer it over software-security_sbom-vulnerability-match or malicious-dependency-check, and no stated prerequisites beyond payment.

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