Skip to main content
Glama

BRAINIAC Software Supply Chain Security

Check licence compatibility

software-security_license-compatibility-check
Read-onlyIdempotent

Read licence identifiers declared in the SBOM or published by npm, PyPI, crates.io, or RubyGems, then compare them with the caller allow and deny policy. Missing identifiers are not treated as compatible. Price $0.05 USDC. POST /api/v1/software-security/license-compatibility-check. 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_license-compatibility-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
sbomNosbom, string, length 2 to 400000. Optional.
policyNopolicy, object. 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 cover read-only, open-world, idempotent, non-destructive, so the added value is in the description: it discloses the fail-closed rule ('missing identifiers are not treated as compatible') and the full x402 payment flow, including that an unpaid call returns payment terms and does not execute. That is meaningful behavior beyond the annotations. It stops short of explaining precedence between the sbom and components inputs, or what happens when neither is supplied despite zero required parameters.

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 core action and the fail-closed rule before the operational details (price, endpoint, payment failure mode). The endpoint string and price are boilerplate-adjacent but earn their place for an agent that must construct a paid call.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. The description covers data sources, policy semantics, and payment behavior, which is nearly everything for a read-only checker. The remaining gap is the input-mode question: with zero required parameters and both 'sbom' and 'components' optional, an agent is left unsure which to supply or whether either is mandatory.

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 all three top-level parameters and the nested component fields. The description adds the useful signal that licence data may come either from the SBOM blob or from npm/PyPI/crates.io/RubyGems lookups, but it does not clarify the sbom-vs-components relationship or the ecosystem field's role. Baseline 3 is appropriate.

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?

Uses a concrete verb pair (read + compare) against a named resource (licence identifiers from SBOM or registry metadata) and states the comparison target (caller allow/deny policy). Purpose is unmistakable to an agent, though it never names or contrasts the sibling tools (kev-exposure-check, malicious-dependency-check, sbom-vulnerability-match) that an agent choosing among security checks would need to disambiguate against.

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?

Implies usage through the phrase 'compare them with the caller allow and deny policy,' which tells the agent this is a policy-gating call rather than a vulnerability scan. However, there is no explicit when-to-use, no when-not-to-use, and no routing to an alternative tool, so an agent must infer its slot in the workflow.

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