Skip to main content
Glama

reward_status

Check Xahau account reward opt-in status, view accrued XAH with exact formula, next claim time, and overdue status. Returns unsigned ClaimReward transaction when applicable.

Instructions

Balance Adjustment doctor — the full answer to Xahau's most common retail question: is this account opted in to network rewards, how much XAH is accrued (EXACT genesis reward-hook formula — reward.c — with live RR/RD read from genesis hook state), when can it next claim, and is the claim overdue (late claiming forfeits yield — the hook pays the per-claim rate once regardless of wait). Returns an unsigned opt-in or claim ClaimReward when applicable. Read-only; 3 serial RPC reads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesr-address
networkNomainnet

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
notesNo
fieldsNo
paramsNo
accrualNo
addressNo
networkNo
optedInNo
summaryNo
warningsNo
balanceXahNo
unsignedTxNo
eligibilityNo
unsignedTxPurposeNo
Behavior5/5

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

The description explicitly states the tool is 'Read-only', performs '3 serial RPC reads', and returns 'an unsigned opt-in or claim ClaimReward when applicable'. It also details the calculation formula, providing full transparency despite no annotations being present.

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 informative but somewhat verbose with phrases like 'Balance Adjustment doctor' and 'EXACT genesis reward-hook formula'. Essential information is front-loaded, but it could be more concise.

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?

The description covers all essential aspects: what the tool does, the information it provides, its read-only nature, the number of RPC calls, and what it returns. Since an output schema exists, the absence of specific return field details is not a gap.

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 has 50% description coverage, with basic descriptions for 'address' and 'network'. The tool description does not add parameter-specific details beyond the schema, but the context (account address and network) is clear from the tool's purpose.

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 clearly states the tool's purpose: checking reward status for Xahau accounts, including opt-in status, accrued amount, claim timing, and overdue status. It distinguishes itself from siblings like 'compute_reward' by offering a comprehensive 'full answer' including unsigned transaction generation.

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?

The description indicates this tool is 'the full answer' for retail reward queries, implying it should be the primary tool for such needs. It mentions 'Read-only' and '3 serial RPC reads' but does not explicitly list when not to use it or provide alternative tool names.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Hugegreencandle/xahau-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server