Radix Community

Get an Olympia token

olympia_get_token

Read-only

An Olympia token: name, symbol, description, web, icon, granularity, whether its supply was fixed or owner-controlled, owner, total supply, minted and burnt, holders count and the largest holders when Olympia ended, plus the Babylon resource it was migrated to. Accepts the rri or the Babylon resource_rdx1… address. 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": {
      "token": "<token>",
      "holders": "<holders>"
    },
    "name": "olympia_get_token"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes	Olympia token rri (e.g. xrd_rr1qy5wfsfh) or the Babylon resource it was migrated to (resource_rdx1…)
`holders`	Yes	Largest holders to list (0-100)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

B3/5.0

Behavior4/5

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

Annotations already state readOnlyHint=true, so 'Read-only' is redundant, but the description adds genuinely non-derivable behavior: the holder data (count and largest holders) reflects state 'when Olympia ended,' telling an agent this is an archival snapshot rather than live data. It does not cover failure modes for an unknown rri, but the historical-scope disclosure is substantive.

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 single sentence is dense but informative; however it front-loads a long field enumeration and buries the actual input contract mid-sentence. The field list could be tightened, and the 'Read-only' close repeats the annotation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, enumerating returned fields is the right move and largely discharges the return-value burden. What remains missing is selection context versus the many sibling lookup tools and any indication of what happens when a token is not found or was never migrated.

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?

Schema description coverage is 100%, so both parameters are already documented with types, default, and 0-100 bounds. The description restates that the token can be an rri or a Babylon resource address and that holders are 'largest holders,' adding no syntax, format, or edge-case detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a noun phrase ('An Olympia token: name, symbol, description...') that enumerates returned fields rather than stating a verb. The operative part is 'Accepts the rri or the Babylon resource_rdx1… address,' which clarifies input but leaves the action and its distinction from siblings like olympia_lookup, lookup_entity, and get_resource_holders implicit.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over olympia_lookup, lookup_entity, get_resource_holders, or olympia_from_babylon. The only usage-adjacent statement is 'Read-only,' which is a safety note, not a selection rule.

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?