Skip to main content
Glama

Rightshold

by com.rightshold
OverviewDiscussionsAdmin

Check many inputs at once

check_rights_batch

Call before shipping anything that bundles third-party assets. Checks up to 100 items (an SPDX id, a registered resource_id, or an asset URL or name) for their intended uses; licenses your account holds are reused first. Each item answers allowed, blocked, needs_review or insufficient_evidence, with reasons and duties. Free, no key. Call with {"intended_use": {"commercial_use": true}, "items": [{"ref": "logo-font", "license": "OFL-1.1"}, {"ref": "hero-photo", "license": "CC-BY-NC-4.0"}]}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
api_keyNoDeprecated: use Authorization: Bearer <key>. With a key the assessment is kept in your account.
intended_useNoIntended 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
itemsYes
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / api_key / deprecated
      Added value: +true
    • changedInput schema / properties / api_key / description
      Previous value: -"Optional: your Rightshold API key, so the assessment is kept in your own account (otherwise it is kept in the public workspace). Not needed if your MCP client sends Authorization: Bearer <key>."New value: +"Deprecated: use Authorization: Bearer <key>. With a key the assessment is kept in your account."
    • 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 / items / items / 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}"
  2. Changed2 schema fields changed
    • addedOutput schema / properties
      Added value: +{
+  "items": {
+    "items": {
+      "properties": {
+        "answer": {
+          "enum": [
+            "allowed",
+            "blocked",
+            "needs_review",
+            "insufficient_evidence"
+          ]
+        },
+        "duties": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "ref",
+        "answer"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "summary": {
+    "properties": {
+      "all_clear": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "total",
+      "all_clear"
+    ],
+    "type": "object"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "items",
+  "summary"
+]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "type": "object"
+}
  4. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The description discloses useful operational context the annotations do not: cost ('Free, no key'), auth posture, and the reuse of licenses already held on the account. Annotations already carry the safety profile (readOnlyHint=false, destructiveHint=false), so this is adequate rather than rich; no rate-limit or storage detail is given.

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?

Four tight sentences, front-loaded with the trigger ('Call before shipping'), then behavior, then output states, then an example. No filler, though the example sentence is somewhat long.

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 3-parameter batch tool with an output schema already documenting return values, the description covers purpose, trigger, input options, and outcome states. Prerequisites beyond 'no key' and limits other than the 100-item cap are the only notable omissions.

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 only 67% schema coverage and bare string params in the schema, the description compensates by explaining that each item can be an SPDX id, registered resource_id, or asset URL/name, and provides a concrete example call. This meaningfully reduces ambiguity about how to fill 'items'.

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?

States a specific verb and resource: 'Checks up to 100 items ... for their intended uses', with the accepted input kinds enumerated. It clearly reads as a batch counterpart to single-item checks like assess_resource_for_use, though it does not name those siblings explicitly.

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?

'Call before shipping anything that bundles third-party assets' gives a clear trigger context. It stops short of naming when-not-to-use or which sibling to prefer for single items.

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