Skip to main content
Glama

AutoTasker Hub — China Social Data API

spdx_licenses

Full SPDX license list (500+ licenses). Compliance/legal aid. $0.01 USDC.

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_licenses"
  }
}

Input Schema

NameRequiredDescriptionDefault
licenseIdNoOptional filter: MIT, Apache-2.0 etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations present the description must carry the behavioral load, and it does contribute two genuinely useful facts beyond structured data: the dataset size (500+ licenses, implying a large payload) and the per-call price of $0.01 USDC. It does not disclose return shape, matching semantics for the filter (exact vs substring), or error behavior for an unknown licenseId, which matter for a zero-annotation tool.

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?

Three short fragments with no filler; the resource and its size lead, followed by purpose and then cost. It is telegraphic to the point that a few clauses of substance (filter behavior) were dropped, but nothing present is wasteful.

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?

For a one-optional-parameter lookup with no output schema and no annotations, the description covers the dataset, its size, its purpose, and its cost — most of what an agent needs. The remaining gap is that it never clarifies the default (all licenses) versus filtered behavior or what a match looks like, leaving a small but real ambiguity.

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% and the single parameter licenseId is documented with examples (MIT, Apache-2.0), so the baseline of 3 applies. The description adds nothing about the filter — it never mentions it or what omitting it returns — so it does not extend parameter meaning beyond the schema.

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?

"Full SPDX license list (500+ licenses)" names the exact resource and its scope/size, so an agent knows it retrieves the canonical SPDX license catalog rather than computing or validating a license. It does not explicitly say whether the result is filtered or complete by default, and it lacks a verb, but the resource is unambiguous and unlike any sibling in the catalog.

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?

"Compliance/legal aid" implies the domain of use (license identification for compliance work) but gives no explicit when-to-use vs when-not conditions, no mention of how the optional filter changes behavior, and no alternatives. Usage is only inferable, not stated.

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.