Skip to main content
Glama

Spdx License Get License Text

spdx_license_get_license_text
Read-onlyIdempotent

Get the full license text for a single SPDX license id (returns standard text + cross-references).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "GPL-3.0-or-later"
    },
    "name": "spdx_license_get_license_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
nameYesFull license name
seeAlsoNoCross-reference URLs
licenseIdYesSPDX license identifier
licenseTextYesFull license text
standardLicenseHeaderNoStandard license header if available

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds the return shape (standard text plus cross-references), but says nothing about invalid-id behavior, text size, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence with the verb and resource front-loaded and the a useful return-content note tucked into parentheses. Nothing is redundant.

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?

Because an output schema exists, the description need not explain return values, and the annotations handle safety. For a simple single-parameter lookup this is close to sufficient, but the identifier semantics and invalid-input behavior are left thin.

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?

The single 'id' parameter has no schema description (0% coverage), so the description's phrase 'SPDX license id' is the only statement of what form of identifier is expected. It still gives no format rules, casing, or validity guidance beyond the example embedded in 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?

States a specific verb and resource: retrieves full license text for a single SPDX license id, and parenthetically notes the payload (standard text plus cross-references). It does not explicitly contrast with siblings such as spdx_license_search, get_license, or list_licenses.

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?

Implicitly scoped to a single, known license id ('a single SPDX license id'), which hints the search-based sibling is for discovery, but it never states when to use this versus spdx_license_search or get_license, nor any exclusions.

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.