Rightshold

Write the attribution line for a license

attribution_string

Read-onlyIdempotent

Call when you reuse material that requires credit. Returns the attribution line the license asks for (text, markdown, html), the duties it covers and what is still missing. Free, no key. Call with {"license": "CC-BY-4.0", "title": "Sunset", "author": "A. Photographer", "source_url": "https://example.org/sunset"}.

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": {
      "license": "<license>"
    },
    "name": "attribution_string"
  }
}

Input Schema

Name	Required	Description
`title`	No	Work title
`author`	No	Creator
`changes`	No	What you changed
`license`	Yes	SPDX id
`source_url`	No	Where it came from

Output Schema

Name	Required	Description	Default
`text`	Yes
`missing`	No
`required`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 20, 2026
- addedInput schema / properties / author / description
```
Added value: +"Creator"
```
- addedInput schema / properties / changes / description
```
Added value: +"What you changed"
```
- addedInput schema / properties / license / description
```
Added value: +"SPDX id"
```
- addedInput schema / properties / source_url / description
```
Added value: +"Where it came from"
```
- addedInput schema / properties / title / description
```
Added value: +"Work title"
```

Changed2 schema fields changedOct 17, 2026

addedOutput schema / properties

Added value: +{
+  "missing": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "required": {
+    "type": "boolean"
+  },
+  "text": {
+    "type": "string"
+  }
+}

addedOutput schema / required

Added value: +[
+  "license",
+  "required",
+  "text"
+]

AddedOct 15, 2026

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, so the bar is lower, and the description still adds real value: output variants (text, markdown, html), the fact that duties and missing items are returned, and 'free, no key' auth context. It does not discuss rate limits or license-id failure behavior.

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 short sentences: trigger first, then return shape, then a concrete example. Nothing is repeated and every sentence earns its place.

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 single required parameter tool with an output schema and full annotation coverage, the description is nearly sufficient. A note on what happens with an unknown SPDX id would close the last gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the worked example call demonstrates how license, title, author and source_url combine in practice, and the SPDX-id hint anchors the one required parameter. That is meaningful added meaning beyond 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 and resource: it returns the attribution line a license requires, in three formats, plus duties and gaps. An agent can immediately tell this apart from check_license or license_compatibility, which do not produce attribution text.

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 when you reuse material that requires credit' gives a clear triggering condition. It does not name an alternative tool or state when not to use it, so it stops short of full routing guidance.

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

All Rightshold tools Inspect

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

Need Help?