Skip to main content
Glama

Spdx License

by io.github.pipeworx-io

Get License

get_license
Read-onlyIdempotent

Get metadata + descriptors for one SPDX license id (e.g. "MIT", "Apache-2.0", "GPL-3.0-or-later").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFull license name
seeAlsoNoCross-reference URLs
licenseIdNoSPDX license identifier
referenceNoReference URL
detailsUrlNoDetails URL
isFsfLibreNoWhether FSF Free/Libre
licenseTextNoFull license text
isOsiApprovedNoWhether OSI approved
referenceNumberNoReference number
isDeprecatedLicenseIdNoWhether license is deprecated
standardLicenseHeaderNoStandard license header if available

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "MIT"
+  },
+  {
+    "id": "Apache-2.0"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "detailsUrl": {
+      "description": "Details URL",
+      "type": "string"
+    },
+    "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"
+    },
+    "licenseText": {
+      "description": "Full license text",
+      "type": "string"
+    },
+    "name": {
+      "description": "Full license name",
+      "type": "string"
+    },
+    "reference": {
+      "description": "Reference URL",
+      "type": "string"
+    },
+    "referenceNumber": {
+      "description": "Reference number",
+      "type": "integer"
+    },
+    "seeAlso": {
+      "description": "Cross-reference URLs",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "standardLicenseHeader": {
+      "description": "Standard license header if available",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds that it returns metadata+descriptors and is scoped to a single ID, but it does not disclose behavior for invalid IDs, case sensitivity, or normalization of the input. This is a moderate addition beyond annotations.

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, well-structured sentence that leads with the action ('Get metadata + descriptors'), states the scope, and provides illustrative examples. Every element earns its place; there is no fluff or unnecessary details.

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 lookup tool with one parameter, strong annotations, and an output schema, the description is sufficient. It covers what the tool does, the scope, and the parameter format. The only minor gap is the lack of explicit reference to sibling tools for alternative needs, but that is not essential for a straightforward operation.

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?

With schema description coverage at 0%, the description must compensate. It does so by explaining that 'id' is an SPDX license ID and providing examples ('MIT', 'Apache-2.0', 'GPL-3.0-or-later'), which give concrete meaning to the otherwise bare string type. It does not cover edge cases like case sensitivity, but the examples establish the expected format.

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's purpose: 'Get metadata + descriptors for one SPDX license id'. It specifies the resource (SPDX license), the scope (one ID), and the type of data (metadata + descriptors). This distinguishes it from siblings like list_licenses (all licenses) and get_license_text (the full text), with the examples reinforcing the intended input format.

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?

The description implies when to use it: when you need metadata/descriptors for a single, specific SPDX license ID. The phrase 'one SPDX license id' signals that this is not for listing or browsing. However, it does not explicitly name alternatives or exclusions (e.g., 'for full text, use get_license_text'), so it lacks explicit when-not guidance.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Many tools have overlapping purposes, such as multiple 'ask_pipeworx' variants, several company analysis tools, and multiple prediction market tools. The set is large and not well-disambiguated, leading to potential confusion.

Naming Consistency2/5

Naming conventions are mixed, with snake_case ('get_license'), camelCase ('ai_visibility_check'), and prefix-based ('pipeworx_*', 'polymarket_*'). No consistent pattern across the tool set.

Tool Count2/5

35 tools is excessive for a server named 'Spdx License', which implies a focused license management tool. The actual number is more appropriate for a general data platform, but mismatched with the server name.

Completeness1/5

For the implied SPDX license domain, only a few basic tools exist (list, get, search). Missing crucial features like create, update, delete, or compare licenses. The surface is severely incomplete for the stated purpose.

Resources