Radix Community

Get an Olympia account at a past date

olympia_get_account_at

Read-only

What an Olympia account held at one point of Olympia, not only at its end: liquid XRD, every token balance and its stakes per validator (staked, pending stake, unstaking), valued as the official Olympia Gateway values them at that state version. Give a UTC day (read at its last state version) or an exact state version. Accepts the rdx1… address or the account_rdx1… it became. 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_account_at"
  }
}

Input Schema

Name	Required	Description
`day`	No	UTC day of Olympia, YYYY-MM-DD (2021-07-26 to 2023-09-28); read at its last state version
`address`	Yes	Olympia account address (rdx1…) or the Babylon account it became (account_rdx1…)
`stateVersion`	No	Exact Olympia state version, instead of a day

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?

Annotations already declare readOnlyHint=true, and the description reinforces read-only while adding substantive behavior: the result is valued as the official Olympia Gateway values it at the chosen state version, and a day is read at its last state version. It does not cover error behavior or rate limits, but for a read-only historical lookup the added context is solid.

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?

The description is compact and front-loads the returned data before the input instructions. The first sentence is dense but every clause contributes to scope or return semantics; 'Read-only' is slightly redundant with annotations but harmless.

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 three-parameter read-only historical lookup with no output schema, the description explains what is returned and how the temporal selector works. It could more explicitly route callers away from olympia_get_account for current/end-state queries, but it is otherwise complete.

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 coverage is 100%, so the schema already documents the day range, address forms, and stateVersion bounds. The description restates the day/stateVersion alternative and address acceptance but adds no format or constraint detail beyond the schema; baseline 3 is appropriate.

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 retrieval of an Olympia account's holdings at a historical point, enumerates the returned balances and stakes, and distinguishes it from an end-of-Olympia snapshot by saying 'not only at its end.' An agent can identify the resource and temporal scope without opening the schema.

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 tells the caller to supply either a UTC day or an exact state version and notes both accepted address forms. It implies the historical-use case versus the sibling olympia_get_account but does not explicitly name that alternative or state when not to use this tool.

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?