Skip to main content
Glama

Rightshold

by com.rightshold
OverviewDiscussionsAdmin

Check a use against a license

check_license
Read-onlyIdempotent

Call before using any image, text, dataset, code, font or model you did not create. Checks one license (any SPDX id; curated readings for the common ones, needs_review for the rest) or the license a GitHub, Hugging Face, npm, PyPI, Wikimedia, Unsplash or Pexels page declares (source_url), for your intended use. Returns permitted, prohibited, needs_review or not_documented, with duties and an uncertainty block (what the verdict leaves open; whether a human must review). Free, no key. Call with {"license": "CC-BY-4.0", "intended_use": {"commercial_use": true, "attribution_planned": true}}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
licenseNoSPDX id, e.g. CC-BY-NC-4.0 (uncurated ids answer needs_review)
source_urlNoInstead of license: a page on GitHub, Hugging Face, npm, PyPI, Wikimedia Commons, Unsplash or Pexels; the license it declares is checked
intended_useYesIntended use: every true flag is a right the check must find documented; omitted flags are false; unknown fields are refused. For instance {"commercial_use":true,"deployment":true,"attribution_planned":true,"duration_days":365}

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dutiesNo
licenseNo
verdictYes
findingsYes
uncertaintyNo
uses_evaluatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / intended_use / description
      Previous value: -"Intended use. Every true flag is a right the assessment must find documented; omitted flags are false. Unknown fields are refused (invalid_intended_use). For instance {\"commercial_use\":true,\"deployment\":true,\"attribution_planned\":true,\"duration_days\":365}"New value: +"Intended use: every true flag is a right the check must find documented; omitted flags are false; unknown fields are refused. For instance {\"commercial_use\":true,\"deployment\":true,\"attribution_planned\":true,\"duration_days\":365}"
    • changedInput schema / properties / license / description
      Previous value: -"SPDX id, e.g. CC-BY-NC-4.0 or Apache-2.0 (any SPDX License List id; uncurated ones answer needs_review)"New value: +"SPDX id, e.g. CC-BY-NC-4.0 (uncurated ids answer needs_review)"
    • addedOutput schema / properties / uncertainty
      Added value: +{
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • addedOutput schema / properties
      Added value: +{
+  "duties": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "findings": {
+    "type": "array"
+  },
+  "license": {
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "reference_hash": {
+        "type": "string"
+      }
+    },
+    "type": [
+      "object",
+      "null"
+    ]
+  },
+  "uses_evaluated": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "verdict": {
+    "enum": [
+      "permitted",
+      "prohibited",
+      "needs_review",
+      "not_documented"
+    ]
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "verdict",
+  "findings"
+]
  3. Changed3 schema fields changed
    • changedInput schema / properties / license / description
      Previous value: -"SPDX id, e.g. CC-BY-NC-4.0 or Apache-2.0"New value: +"SPDX id, e.g. CC-BY-NC-4.0 or Apache-2.0 (any SPDX License List id; uncurated ones answer needs_review)"
    • addedInput schema / properties / source_url
      Added value: +{
+  "description": "Instead of license: a page on GitHub, Hugging Face, npm, PyPI, Wikimedia Commons, Unsplash or Pexels; the license it declares is checked",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "license",
-  "intended_use"
-]New value: +[
+  "intended_use"
+]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "type": "object"
+}
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations: it discloses that the service is free and needs no key, that curated readings exist for common ids while others return needs_review, the full verdict vocabulary plus duties and an uncertainty block, and the platform allow-list for source_url. The annotations cover safety; the description covers coverage limits, cost/auth, and answer shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the imperative call-to-action and the what-it-checks clause before the return-value detail, so the critical routing information comes first. It is a dense single block and the trailing example duplicates schema guidance, but nearly every clause carries load.

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 tool with a nested object parameter, two mutually exclusive input paths, and an output schema, the description supplies the missing behavioral context: coverage boundaries, auth/cost, verdict set, and the uncertainty block. Nothing an agent needs to invoke it correctly is absent.

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 coverage is already 100%, so the baseline is 3, but the description adds real meaning: license vs source_url are presented as alternatives, the curated-vs-needs_review behavior of arbitrary SPDX ids is explained, and a concrete worked invocation shows the intended_use nesting. Little more could be added beyond field-level semantics already in the schema.

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 (check) and resource (a license), and specifies both input modes: a raw SPDX id, or the license declared by a page on a named set of hosts. The scope note 'one license' implicitly separates it from batch siblings like check_rights_batch and from license_compatibility or assess_resource_for_use.

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?

Opens with an explicit trigger: 'Call before using any image, text, dataset, code, font or model you did not create,' which is exactly the context an agent needs. It does not, however, name a sibling alternative or state when to prefer a different tool (e.g., batch or multi-license checks), so routing above the single-license case is left to inference.

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

All Rightshold 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