Skip to main content
Glama

Get an Olympia account’s staking rewards

olympia_get_account_rewards
Read-only

An Olympia account’s staking rewards in one year, per day and validator: what it earned as a delegator and, if it owned a validator, the fee. Totals included. 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>",
      "year": "<year>"
    },
    "name": "olympia_get_account_rewards"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesCalendar year, 2021 to 2023
addressYesOlympia account address (rdx1…) or the Babylon account it became (account_rdx1…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the trailing 'Read-only' merely restates that. The description does add useful substance the annotations cannot: the result is bucketed per day and per validator and includes totals, plus a conditional fee section when the account owned a validator. It says nothing about pagination, missing-data behavior for years without activity, or how the Babylon address mapping affects results.

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?

A single front-loaded sentence states the resource and the result shape with no wasted clauses; the only weak element is the redundant trailing 'Read-only' that duplicates the annotation.

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 tool with full schema coverage and no output schema, the description is nearly sufficient: it explains the output's structure (per day, per validator, delegator plus fee, totals). Minor gaps remain around result ordering, empty-year handling, and the distinction from sibling reward/account tools.

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 both parameters are documented in the schema, including the 2021–2023 year bounds and the rdx1/account_rdx1 address duality. The description echoes the one-year scope but adds no extra constraint, default, or format detail beyond what the schema already provides, so the baseline 3 applies.

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?

The description names a specific verb (get) and resource (Olympia account staking rewards) and scopes it precisely to one year, broken down per day and per validator, with delegator earnings and validator fee distinguished. That granularity separates it from account-level siblings like olympia_get_account and validator-level ones like olympia_get_validator_rewards, though it never names an alternative explicitly.

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?

Usage is only implied: 'in one year, per day and validator' signals this is the granular reward breakdown tool. There is no explicit statement of when to prefer this over olympia_get_validator_rewards, olympia_get_account_at, or the general account tools, and no prerequisites or exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources