Skip to main content
Glama

Spdx License Search

spdx_license_search
Read-onlyIdempotent

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

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": {
      "query": "Apache"
    },
    "name": "spdx_license_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
countYesNumber of matching licenses
queryYesLowercase search query string
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuine behavioral detail beyond that: matching is substring (partial, not exact) and case-insensitive, and it spans both the id and the full name fields. Return values need not be described since an output schema exists.

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, front-loaded with the operation and followed immediately by the searched fields and matching semantics. No filler or redundant restatement of the tool name.

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 one-parameter lookup with a full output schema and rich annotations, the definition covers everything needed to call it correctly. The only shortfall is the absence of explicit routing guidance toward the sibling license-text tool.

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?

Schema description coverage is 0%, so the description must carry the meaning of the single 'query' parameter, and it does by stating that the value is matched as a substring against both SPDX id and full license name, case-insensitively. The schema's examples ('Apache', 'BSD') further illustrate typical inputs, leaving little ambiguity.

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?

Names a specific operation ('Substring search') and the exact fields searched ('SPDX id and full license name'), so the agent knows precisely what resource is being matched. It does not explicitly exclude the sibling spdx_license_get_license_text, but the search-vs-fetch distinction is inferable from the wording.

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 is only implied: the agent can infer this is the tool for finding a license by partial name or id. There is no explicit statement of when to prefer it over 'get_license_text' or other license tools, and no prerequisites or exclusions are given.

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.