Skip to main content
Glama

Spdx License

by io.github.pipeworx-io
OverviewDiscussionsAdmin

List Licenses

list_licenses
Read-onlyIdempotent

List SPDX licenses with optional filters (OSI-approved, FSF Free/Libre, deprecated).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fsfLibreNo
deprecatedNoInclude deprecated. Default false.
osiApprovedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of licenses in filtered results
licensesYes
releaseDateYesRelease date of the license list
licenseListVersionYesVersion of the SPDX license list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "osiApproved": true
+  },
+  {
+    "deprecated": false,
+    "fsfLibre": true
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of licenses in filtered results",
+      "type": "integer"
+    },
+    "licenseListVersion": {
+      "description": "Version of the SPDX license list",
+      "type": "string"
+    },
+    "licenses": {
+      "items": {
+        "properties": {
+          "isDeprecatedLicenseId": {
+            "description": "Whether license is deprecated",
+            "type": "boolean"
+          },
+          "isFsfLibre": {
+            "description": "Whether FSF Free/Libre",
+            "type": "boolean"
+          },
+          "isOsiApproved": {
+            "description": "Whether OSI approved",
+            "type": "boolean"
+          },
+          "licenseId": {
+            "description": "SPDX license identifier",
+            "type": "string"
+          },
+          "name": {
+            "description": "Full license name",
+            "type": "string"
+          },
+          "reference": {
+            "description": "Reference URL for the license",
+            "type": "string"
+          }
+        },
+        "required": [
+          "licenseId",
+          "name",
+          "isOsiApproved",
+          "isFsfLibre",
+          "isDeprecatedLicenseId",
+          "reference"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "releaseDate": {
+      "description": "Release date of the license list",
+      "type": "string"
+    }
+  },
+  "required": [
+    "licenseListVersion",
+    "releaseDate",
+    "count",
+    "licenses"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety and mutation traits. The description adds the filter dimensions but discloses no extra behavioral details such as pagination, ordering, or default behavior when no filters are applied. The value added is moderate.

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?

The description is a single, front-loaded sentence that states the action and object first, then lists the variable filters. No wasted words or redundant repetition of schema/annotation content.

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?

For a simple list tool with an output schema and strong annotations, the description covers the essential purpose and filter semantics. It might mention the default behavior when no filters are provided, but the absence of that is not a significant gap given the tool's simplicity and the existence of an output schema.

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?

The schema description coverage is low (33% – only 'deprecated' has a description). The description compensates by naming the conceptual filters: OSI-approved, FSF Free/Libre, and deprecated, which adds meaning to osiApproved and fsfLibre. It still leaves the exact boolean semantics implicit, but it is a clear improvement over the schema alone.

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 clearly states the tool lists SPDX licenses, a specific verb+resource combination, and names the optional filters. It distinguishes itself from siblings like get_license and get_license_text by focusing on listing rather than retrieving individual 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?

The description implies when to use the tool (when a list of licenses is needed) and describes the filter options, but it does not explicitly compare with alternatives or exclude other tools like get_license. There is no when-not-to-use guidance, so it stops short of a 4 or 5.

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

All Spdx License toolsInspect
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