Rightshold

Know Your Agent: look up an agent's RS-KYA level

kya_lookup

Read-onlyIdempotent

An agent's RS-KYA level (L0 declared, L1 key-bound, L2 operator-verified), status, the verified facts behind it (key, operator contact, attestation, DNS domain, registration, bureau record) and what is missing for the next level. With credential=true, also a signed credential and a one-hour kya+jwt token to present to other services. Free, no key. Call with {"agent": "RS-XXXX-XXXX"}.

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": {
      "agent": "<agent>"
    },
    "name": "kya_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`agent`	Yes	Registration number (RS-XXXX-XXXX), handle or agent id
`credential`	No	Return the signed credential

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026
- addedInput schema / properties / credential / description
```
Added value: +"Return the signed credential"
```
Changed1 schema field changedOct 14, 2026
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "type": "object"
+}
```
First observedOct 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the bar is lower; the description adds genuinely new behavior: no API key required, and that credential=true unlocks a signed credential plus a one-hour kya+jwt token. The one-hour TTL and downstream presentation use are details structured fields cannot convey.

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?

Opens with the core action and return payload, then layers the credential option and the free/no-key note. Dense but every clause carries information; only the level enumeration is arguably over-packed into the first sentence.

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 two-parameter read-only lookup with an output schema and full annotation coverage, the description covers inputs, the optional credential path, and cost/auth. The remaining gap is sibling disambiguation against kya_check and kya_verify.

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 100%, so baseline is 3; the description goes beyond the schema's bare 'Return the signed credential' by explaining that credential=true also yields a one-hour kya+jwt token for presenting to other services. It also supplies a concrete call shape for the required agent parameter.

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 ('look up an agent's RS-KYA level') and enumerates the levels (L0/L1/L2) plus the returned facts, so the agent knows exactly what it gets. It does not, however, distinguish itself from the sibling tools kya_check and kya_verify, which plausibly overlap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an invocation example and notes 'Free, no key,' which gives basic usage context. There is no explicit when-to-use/when-not guidance and no routing between this and kya_check/kya_verify, leaving the choice to inference.

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?