Skip to main content
Glama

Rightshold

by com.rightshold
OverviewDiscussionsAdmin

Can these licenses be combined?

license_compatibility
Read-onlyIdempotent

Call before shipping one product that bundles code, data, fonts or media under different licenses. Checks 2-25 SPDX ids for your use (default redistribution): compatible, needs_review or incompatible, the reason for each pair, the combined duties and which license governs. Free, no key. Call with {"licenses": ["MIT", "GPL-3.0-only", "CC-BY-NC-4.0"], "intended_use": {"redistribution": true, "commercial_use": true}}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
licensesYes
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
pairsYes
verdictYes
combined_dutiesNo

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 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: +{
+  "combined_duties": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "pairs": {
+    "items": {
+      "properties": {
+        "verdict": {
+          "enum": [
+            "compatible",
+            "needs_review",
+            "conflict"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "verdict": {
+    "enum": [
+      "compatible",
+      "needs_review",
+      "incompatible"
+    ]
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "verdict",
+  "pairs"
+]
  3. Added

TDQS

A4.5/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 closed-world, so the safety profile is covered. The description adds genuinely new context: that it is free with no key required, and that results classify each pair and name combined duties and the governing license.

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?

Three sentences: the invocation trigger first, then the returned classification, then a literal example. Every clause carries information (constraints, defaults, sample payload) with no filler.

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 nested-input tool with an output schema, the description supplies the missing pieces an agent needs: when to call, the id count bounds, the default intended_use, and a concrete payload. Return values need not be explained further because an output schema exists.

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 50%, and the schema itself documents intended_use flag semantics, geography and duration_days, but leaves 'licenses' undocumented. The description compensates by stating the 2-25 SPDX id range, the default use case ('default redistribution'), and a full example call including intended_use.

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 2-25 SPDX ids' for combining licenses) plus the outcome vocabulary (compatible / needs_review / incompatible). This distinguishes it from siblings like check_license and assess_resource_for_use, which are not about cross-license combination.

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?

Gives a clear trigger ('Call before shipping one product that bundles code, data, fonts or media under different licenses') and implicitly scopes usage to multi-license bundles. It does not name or exclude any sibling tool, so the agent must infer why this differs from check_license.

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