Skip to main content
Glama

security-crypto

spdx_license_compatibility

Classify SPDX open-source license identifiers (MIT, Apache-2.0, BSD, GPL-3.0, AGPL-3.0) by copyleft tier, patent grant, and commercial risk.

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": "spdx_license_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
licensesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and mostly fails it: nothing says whether unknown or non-SPDX identifiers are rejected, how license expressions (OR/AND, WITH exceptions) are handled, or what the classification output looks like. Only the implicit read-only nature of a classification task is conveyed.

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?

A single front-loaded sentence with no filler, and the enumerated classification axes are efficient. It is terse to the point of under-specification, but there is no wasted wording.

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

Completeness2/5

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

No annotations and no output schema mean the description must explain inputs and results, and it does neither. For a two-parameter tool whose name signals a compatibility check the description never describes, an agent lacks the information to invoke it correctly or interpret its answer.

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

Parameters2/5

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

Schema coverage is 0%, yet the description never mentions either parameter. The list of example identifiers hints at the format expected for 'licenses', but the 'text' parameter (free-form license text? a single identifier?) is entirely unexplained, and the distinction between the two inputs is left to guesswork.

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?

States a specific verb ('classify') and resource ('SPDX open-source license identifiers') plus the exact dimensions of classification (copyleft tier, patent grant, commercial risk). However, the tool name promises 'compatibility' (licenses working together) while the description only describes per-license classification, leaving the core operation ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this rather than sibling audit tools like sbom_inspect_and_audit or package_json_audit, which plausibly also surface license information. There is also no indication whether it evaluates one license or a pair, so the agent cannot infer the intended scenario.

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