Licenses

Get License Text

get_license_text

Read-onlyIdempotent

Fetch the full license text for an SPDX id (e.g. "MIT"). Keyless.

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": {
      "spdx_id": "MIT"
    },
    "name": "get_license_text"
  }
}

Input Schema

Name	Required	Description	Default
`spdx_id`	Yes	An SPDX license id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 29, 2026
- addedInput schema / examples
```
Added value: +[
+  {
+    "spdx_id": "MIT"
+  }
+]
```
First observedJul 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare the tool as read-only and non-destructive. The description adds the term 'Keyless', implying no authentication is needed, which is a useful behavioral hint. However, beyond this, it does not elaborate on response format, error handling, or other traits.

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?

The description is ultra-concise (one short sentence) and front-loaded with the key action and example. It contains no filler, though it could benefit from structured breakdown for complex scenarios. However, for a simple tool, this is effective.

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?

Given the tool's simplicity (one parameter, no output schema), the description is sufficiently complete. It communicates the core function and output type. The missing output specification is acceptable as the return is intuitive ('full license text').

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 input schema already has 100% description coverage for the sole parameter 'spdx_id'. The tool description does not add any additional semantic meaning beyond what the schema provides, so it meets the baseline without enhancement.

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?

The description explicitly states the verb 'Fetch' and the resource 'full license text for an SPDX id', with a concrete example 'MIT'. It clearly distinguishes from siblings like 'search_licenses' by focusing on retrieving the exact license text for a given SPDX identifier.

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?

The description provides no guidance on when to use this tool versus siblings such as 'lookup_license' or 'search_licenses'. It does not specify prerequisites, alternatives, or when not to use it, leaving the agent to infer usage context.

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

All Licenses tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.