ScorpTech x402 API

License Detect

license_detect

Read-onlyIdempotent

Identify a software / content licence from a LICENSE file, source header or SPDX expression and explain what it allows: 40 licences incl. MIT, Apache-2.0, BSD-2/3/4, ISC, 0BSD, GPL/LGPL/AGPL v2/v3, MPL-2.0, EPL, EUPL, Unlicense, CC0, Creative Commons BY/SA/NC/ND, and source-available BUSL / SSPL / Elastic / PolyForm / Commons Clause. Returns SPDX id, confidence, category (permissive, weak / strong / network copyleft, non-commercial, source-available), OSI approval, permissions / conditions / limitations, "or later" detection, SPDX-License-Identifier tags and copyright holders. Offline; not legal advice. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/license-detect

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

Input Schema

Name	Required	Description	Default
`spdx`	No	Or an SPDX licence expression, e.g. "MIT OR Apache-2.0", "GPL-2.0-or-later WITH Classpath-exception-2.0"
`text`	No	LICENSE / COPYING text, README section or source file header

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly/openWorld/idempotent/destructive), disclosing that processing is offline, that the output is not legal advice, and the payment model ('$0.002 USDC per successful call (x402, Solana)') with the equivalent HTTPS endpoint. It also enumerates the actual response fields (SPDX id, confidence, category, OSI approval, permissions/conditions/limitations, 'or later', tags, copyright holders), which the annotations cannot convey.

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?

Front-loaded with the purpose and input forms, then the coverage list, then outputs, then cost/transport. The 40-licence enumeration and field list are long but each is decision-relevant for an agent judging whether coverage matches its licence. Slightly dense as a single run-on paragraph, but no sentence is filler.

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?

With no output schema, the description carries the return-value burden and does so explicitly. It also discloses the pricing/payment requirement and an alternative transport, which are the operational facts an agent needs before invoking a paid, offline tool. Nothing material is missing.

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 already 100% with per-parameter descriptions, so the baseline is 3. The description adds meaning by mapping its three named input forms onto the two parameters: free-text licence/header material goes to 'text' and a structured expression goes to 'spdx', clarifying that either input path is valid.

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 ('Identify') plus resource ('software / content licence') and enumerates the three accepted input forms (LICENSE file, source header, SPDX expression). It goes further to say what the tool explains ('what it allows') and the exact licence families covered, so an agent knows precisely what this does and what it does not cover.

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

Usage Guidelines4/5

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

Clear about when it applies: when you have licence text, a source header, or an SPDX expression. Adds useful caveats ('Offline; not legal advice'). It does not name a competing sibling or state exclusions, but no sibling in this catalogue performs licence identification, so the routing burden is low.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ScorpTech x402 API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?