Rightshold

List toolsets

list_toolsets

Read-onlyIdempotent

The toolsets this server offers and the tools in each. Connect to /mcp?toolset= (or toolset=all) to list them; most clients only offer the tools they listed, so connect with the set your task needs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_toolsets"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "type": "object"
+}
```
First observedOct 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds non-obvious behavior: the result is per-toolset tool membership, and tool availability is fixed at connect time, which is a server/client constraint an agent cannot infer from annotations.

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?

Two sentences, no filler, with the resource statement front-loaded and the actionable connection detail second. The subordinate clause explaining why the connection choice matters is load-bearing, not padding.

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 zero-parameter discovery tool with an output schema (so return shape needn't be described) and full annotation coverage, the description supplies the one thing that is otherwise unguessable: how to actually connect to a toolset. Nothing an agent needs in order to use it correctly is missing.

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?

Zero input parameters means a baseline of 4. The description goes slightly further by documenting the URL-level toolset=<name> / toolset=all selector that is not present in the input schema, which is genuinely useful semantics for the follow-up 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?

The description names the resource precisely ('the toolsets this server offers and the tools in each'), which is enough to distinguish this meta/discovery tool from all the domain siblings (check_license, kya_verify, etc.). It is a nominal fragment with no verb, so it stops short of a 5, but the intent is unambiguous.

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?

It gives concrete operational guidance: connect to /mcp?toolset=<name> or toolset=all, and pick the set your task needs. The rationale ('most clients only offer the tools they listed') explains why this matters. It stops short of a 5 because it never states explicitly when to call this tool versus just calling a known sibling directly.

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?