Skip to main content
Glama

BRAINIAC Software Supply Chain Security

Precheck release security

software-security_release-precheck
Read-onlyIdempotent

Combine exact-version OSV matches, CISA KEV exposure, licence policy, and malicious-package advisories into one release report. The report never approves a release. Price $0.15 USDC. POST /api/v1/software-security/release-precheck. 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_release-precheck"
  }
}

Input Schema

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

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds behavior the agent could not infer: a $0.15 USDC price, x402 payment gating where an unpaid call returns payment terms and does not execute, and a clear caveat that the output is advisory and never an approval. Cost and payment-gate semantics are exactly the kind of operational context annotations cannot carry.

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 tight sentences, front-loaded with the value proposition, followed by the non-approval caveat and then operational details. The raw endpoint path (POST /api/v1/software-security/release-precheck) is transport trivia that mildly dilutes an otherwise waste-free definition.

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?

An output schema exists, so return values need not be explained, and payment behavior is well covered. What is missing for a nested, all-optional-input tool is input-shape guidance — which of sbom vs components drives the check and how policy allow/deny interacts with licence results — leaving the agent to guess at call construction.

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 baseline is 3, and the description adds nothing about sbom, policy, or components. It also leaves the important structural choice unexplained: with zero required parameters, is the caller expected to pass an sbom string, a components array, or both? The schema's own property descriptions are boilerplate ('sbom, string, length 2 to 400000. Optional.'), so the gap is not covered elsewhere.

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 deliverable — combining exact-version OSV matches, CISA KEV exposure, licence policy, and malicious-package advisories into one release report. The enumerated sources implicitly delineate it from the four single-purpose siblings (kev-exposure-check, license-compatibility-check, malicious-dependency-check, sbom-vulnerability-match). An agent can tell this is the aggregate release gate.

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 implied rather than stated: the composition list suggests this is the one-shot aggregate, but the description never says 'use this instead of calling the four checks individually' nor when to prefer a single-check sibling. The only explicit constraint is a negative one — the report never approves a release — which bounds interpretation but does not route tool selection.

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