Skip to main content
Glama
Sign In

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 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}}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "intended_use": "<intended_use>"
    },
    "name": "check_license"
  }
}

Input 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_useYesUses to check: each true flag must be documented; omitted = false; unknown fields refused. For instance {"commercial_use":true}

Output Schema

NameRequiredDescriptionDefault
dutiesNo
licenseNo
verdictYes
findingsYes
uncertaintyNo
uses_evaluatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / intended_use / description
      Previous 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}"New value: +"Uses to check: each true flag must be documented; omitted = false; unknown fields refused. For instance {\"commercial_use\":true}"
  2. 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"
+}
  3. 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"
+]
  4. 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"
+]
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "type": "object"
+}
  6. 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 readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds genuinely new behavior: the four verdict values (permitted/prohibited/needs_review/not_documented), that duties and an uncertainty block are returned, that uncurated SPDX ids fall back to needs_review, and that it is free with no key — context the annotations cannot convey.

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?

The single paragraph is front-loaded with the actionable instruction ("Call before using...") before the mechanics and the example. It is dense and slightly repetitive — the provider list and the curated-vs-needs_review rule are restated from the schema — but every sentence carries information.

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?

With a full input schema, an output schema, and rich annotations, the description covers purpose, inputs, verdict vocabulary and the uncertainty block, which is what an agent needs to call and interpret it. The one gap is that it never states what happens if both license and source_url are omitted, a real possibility given only intended_use is required.

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 100%, so baseline is 3; the description goes slightly beyond by framing license and source_url as alternatives ("Instead of license" is only in the schema) and by giving a concrete call example showing how license nests with intended_use. It does not clarify the error behavior when neither license nor source_url is supplied, though only intended_use is required.

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 ("Checks one license") plus the two mutually exclusive input modes (an SPDX id, or a source_url whose declared license is read) and the intended-use qualifier. It is clearly distinguishable from siblings like license_compatibility (pairwise compatibility) and check_rights_batch (multi-item), which an agent could otherwise confuse with this single-check tool.

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 tells the agent exactly when this is the right tool. It does not explicitly exclude cases or route to alternatives such as check_rights_batch for multiple items, so it stops short of full when/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 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