Skip to main content
Glama

Spdx License

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search

search
Read-onlyIdempotent

Substring search across SPDX id and full license name (case-insensitive).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of matching licenses
queryYesLowercase search query string
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "Apache"
+  },
+  {
+    "query": "BSD"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of matching licenses",
+      "type": "integer"
+    },
+    "query": {
+      "description": "Lowercase search query string",
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "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"
+          },
+          "name": {
+            "description": "Full license name",
+            "type": "string"
+          },
+          "reference": {
+            "description": "Reference URL",
+            "type": "string"
+          },
+          "referenceNumber": {
+            "description": "Reference number",
+            "type": "integer"
+          },
+          "seeAlso": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "count",
+    "results"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent behavior. The description adds valuable behavioral context: substring matching, case-insensitivity, and the two fields searched, which go beyond the structured metadata. No contradictions detected.

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?

A single, front-loaded sentence conveys all key information with no wasted words. Every element earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter, rich annotations, and an output schema, the description adequately covers what the tool does and how it behaves. No additional information is needed for correct invocation.

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 0% schema description coverage, the description compensates by explaining the 'query' parameter is used for substring matching across SPDX IDs and license names. This adds meaning beyond the raw schema, though it could be more explicit about matching rules.

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 states a specific verb ('search') and resource ('SPDX id and full license name') with clear scope (substring, case-insensitive). It distinguishes the tool from siblings like 'get_license' and 'search_within' by defining the exact fields searched.

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?

Usage context is implied: use this tool to find licenses by partial ID or name. However, no explicit comparison to alternatives like 'search_within' or 'list_licenses' is provided, so the agent must infer when this tool is preferred.

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