Radix Community

Get an Olympia validator

olympia_get_validator

Read-only

An Olympia validator as Olympia ended: name, web, owner, node key, fee, registration and delegation, XRD staked and share of the network, owner stake, stake-unit factor, delegators, lifetime uptime and proposals, rewards paid out, the top delegators, its stake over time and its monthly staking activity (XRD staked and unstaked). Read-only.

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": {
      "address": "<address>"
    },
    "name": "olympia_get_validator"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	Olympia validator address (rv1…)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description adds significant behavioral context by detailing the complex nature of the returned data, such as 'stake over time' and 'monthly staking activity,' which goes beyond the simple 'readOnlyHint' annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is necessarily long to list every attribute retrieved, making it detailed but not concise. However, every sentence is critical to understanding the tool's output and justifies its length.

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?

Given that the tool returns a large, complex set of data (including historical stake data), the description is maximally complete, ensuring an agent knows precisely what output to expect.

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

Parameters3/5

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

The input schema coverage is 100%, meaning all parameter details are covered structurally. The description does not add any meaningful semantic context or guidance regarding the single 'address' parameter.

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 is highly specific, listing a comprehensive array of attributes (name, web, owner, stake over time, rewards) that define the purpose of this tool as a master validator record retriever.

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?

While it does not explicitly name alternative tools, the exhaustive list of returned data defines the perfect use case for this tool—retrieving a full, complex snapshot of a validator.

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

All Radix Community 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?