Skip to main content
Glama
Sign In

Rightshold

by com.rightshold
OverviewDiscussionsAdmin

Ask Rightshold (plain English)

ask_rightshold

Call when you have a rights or licensing question in plain English, such as 'Can I use CC BY-NC 4.0 images in a paid ad campaign?'. Returns the license or registered resource and the use it understood, and a deterministic answer with reasons; it asks for clarification instead of guessing. Check the understood use before relying on it. Free, no key.

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": {
      "question": "<question>"
    },
    "name": "ask_rightshold"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesPlain-language rights question
resource_idNoOptional: pin a registered resource instead of letting the interpreter match one.
intended_useNoUses to check: each true flag must be documented; omitted = false; unknown fields refused. For instance {"commercial_use":true}

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / api_key
      Removed value: -{
-  "deprecated": true,
-  "description": "Deprecated: use Authorization: Bearer <key>. With a key the assessment is kept in your account.",
-  "type": "string"
-}
    • 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}"
    • addedInput schema / properties / question / description
      Added value: +"Plain-language rights question"
  2. Changed3 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}"
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "type": "object"
+}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only cover safety flags, and the description adds genuinely useful behavior: deterministic answering with reasons, a clarification-instead-of-guessing fallback, a caveat to verify the interpreted use, and an auth/cost note ('Free, no key'). It does not explain pagination or failure modes, but for a single-shot Q&A tool this is well above the annotation baseline.

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?

Front-loaded with the trigger condition, then response shape, then the reliability caveat and cost note. Three dense sentences with no filler; nothing repeats the tool name or title.

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?

An output schema exists, so return values need little prose, yet the description still frames them. Auth, cost, clarification behavior, and the interpretation caveat are all covered, leaving no gap an agent needs closed before invoking.

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 description coverage is 100%, so the baseline is 3. The description still adds interpretive meaning beyond the schema: that resource_id pins a resource the interpreter would otherwise match, and that the returned 'understood use' corresponds to the intended_use flags, telling the agent how to validate the call.

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 ('Call when you have a rights or licensing question') and describes the response shape (license/resource + understood use + deterministic answer with reasons). It implies a natural-language front door relative to structured siblings like check_license or assess_resource_for_use, but never names an alternative, so the differentiation is inferential rather than explicit.

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 clear use context ('plain English' rights question) plus a concrete example question, and adds an output-side guideline: 'Check the understood use before relying on it.' It offers no exclusions or named alternatives, so an agent must infer when to pick check_license or check_rights_batch instead.

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