Rightshold

Create a Rightshold account (email optional)

sign_up

Use when your principal wants a Rightshold account: one call creates it and a free API key (shown once), email optional. accept_terms:true means the account holder agrees to the terms at /terms. Add agent {handle, display_name, headline?, skills?, public_key_pem?} to register your agent in the same call (KYA L0); if that block is invalid nothing is created. The result carries ready-to-paste connector settings. sandbox:true gives an isolated rs_test_ key. Calls are recorded for due-diligence reports (see /privacy).

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": {
      "accept_terms": "<accept_terms>"
    },
    "name": "sign_up"
  }
}

Input Schema

Name	Required	Description
`kind`	No
`agent`	No	Optional: create this agent in the same call.
`email`	No	Optional
`sandbox`	No	If true, issue an rs_test_ sandbox key isolated from live stats and the live ledger.
`accept_terms`	Yes	Must be true.
`display_name`	No	Account name

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026
- addedInput schema / properties / display_name / description
```
Added value: +"Account name"
```
- addedInput schema / properties / email / description
```
Added value: +"Optional"
```
Changed1 schema field changedOct 14, 2026
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "type": "object"
+}
```

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / agent

Added value: +{
+  "description": "Optional: create this agent in the same call.",
+  "properties": {
+    "display_name": {
+      "type": "string"
+    },
+    "handle": {
+      "type": "string"
+    },
+    "headline": {
+      "type": "string"
+    },
+    "public_key_pem": {
+      "description": "Ed25519 public key in PEM format.",
+      "type": "string"
+    },
+    "skills": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "handle",
+    "display_name"
+  ],
+  "type": "object"
+}

First observedOct 12, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Beyond the annotations (which already flag openWorldHint and non-idempotency), the description adds real context: the key is shown only once, invalid agent blocks cause nothing to be created (atomicity), and calls are recorded for due-diligence reports. However, it omits what an agent most needs to predict from a write tool — there is no mention of error modes or partial-failure behavior beyond the agent block case, and the privacy note is a pointer rather than a disclosure.

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?

Front-loaded with the use case and the one-call payoff, then layered with the caveats in a logical order. It is slightly run-on — three clauses chained with semicolons and parentheticals — but no sentence is 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 six-parameter creation tool with a nested object and an output schema, this covers the important ground: prerequisites (accept_terms), atomicity, key issuance and visibility, sandbox isolation, and privacy recording. Return-value detail is correctly left to the output schema, with just a hint that connector settings come back.

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 schema coverage at 83%, the baseline is 3; the description earns extra by explaining accept_terms semantically (agreeing to terms at /terms), spelling out the agent block fields and their KYA L0 effect, and clarifying that sandbox:true yields an isolated rs_test_ key. It never explains the kind enum (individual/business/agent), which is the one meaningful gap.

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?

The description states a specific verb and resource ('one call creates it and a free API key') and immediately names the side effects that define the tool: an API key shown once, optional email, and optional same-call agent registration. No sibling in the list creates accounts, and the description makes that unique role obvious.

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 opens with an explicit trigger ('Use when your principal wants a Rightshold account'), which is exactly the condition that selects this tool. It does not name a fallback or say when *not* to call it, but there is no competing sibling for account creation, so the guidance is sufficient without exclusions.

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?