Skip to main content
Glama

license_detect

Read-only

Identify a common SPDX license (MIT, Apache-2.0, GPL, LGPL, AGPL, BSD, MPL-2.0, ISC, Unlicense, CC0, …) from license text or a public LICENSE file URL. Returns confidence and key permissions/conditions. Not legal advice. Price: 0.003 USDC per call (x402, Base).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "license_detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPublic URL of a LICENSE file
textNoLicense text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnlyHint=true and openWorldHint=true, and the description adds genuinely structured-external facts: the return payload (confidence and key permissions/conditions), a liability disclaimer ('Not legal advice'), and the billing mechanism and cost (0.003 USDC per call via x402 on Base). That payment/auth requirement is exactly the kind of context an agent cannot get from annotations. It does not describe failure modes or behavior when inputs are ambiguous.

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?

Two tight sentences: capability and recognized licenses first, then output, disclaimer, and price. No filler, and the most decision-relevant details (what it returns, what it costs) are not buried.

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 two-optional-parameter read-only classifier with no output schema, the description supplies enough: input modes, output shape, disclaimer, and price. The one meaningful gap is whether 'url' and 'text' are alternatives or can be combined, which the agent must guess.

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?

Schema description coverage is 100%, with 'url' documented as a public LICENSE file URL and 'text' as license text, so the schema already carries the parameter meaning. The description restates those two input modes without adding syntax, precedence, or mutual-exclusivity rules, so the baseline 3 applies.

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?

States a specific verb and resource ('Identify a common SPDX license') and enumerates the recognized license families (MIT, Apache-2.0, GPL, BSD, MPL-2.0, etc.) plus the two accepted input forms. An agent knows exactly what comes back: confidence plus key permissions/conditions. Siblings (check_headers, verify_links, wiki_summary) are unrelated utilities, so no further differentiation is needed.

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 makes the usage context clear: pass license text or a public LICENSE file URL to classify it. It does not state when NOT to use the tool, nor does it address what to do if both inputs are supplied or if the text is not a recognizable license, so guidance stops short of the 5 level.

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.

Resources