Aether testnet wallet

Get miner status

get_miner_status

Read-onlyIdempotent

Check whether an address will become a validator when this epoch ends: its registered consensus key, work this epoch, rank among eligible miners, blocks (and estimated seconds) until the validator set is picked, whether it's a validator now and with what voting power, and its escrowed mining rewards. From block 396,000 seats follow seat work (selectionRule seat_work_power): the difficulty met over the last 3 epochs, native and merged-mined. The address is required. Read-only; every field is as of one block height.

Input Schema

Name	Required	Description	Default
`address`	Yes	Aether account address (aether1...); required, this server holds no key

Output Schema

Name	Required	Description
`rank`	No	1-based position among eligible miners by work (by seat work under seat_work_power); absent if not eligible
`epoch`	Yes
`banned`	Yes	permanently banned for equivocation
`escrow`	Yes
`height`	Yes	every field is as of this block
`address`	Yes
`onTrack`	Yes	would be picked if the epoch ended now; never true under beacon_weighted_sample, since a random draw isn't known in advance
`eligible`	Yes	can be picked when this epoch ends: has work this epoch, a registered consensus key, and no ban
`seatWork`	No	under seat_work_power: the difficulty this address's accepted submissions met over the last 3 epochs, native and merged-mined; it decides seats and power
`topKSize`	Yes
`workShare`	No	0 to 1: this address's share of all eligible work this epoch; under seat_work_power, its share of all the window's seat work, which must be at least 0.01 to qualify
`powerShare`	No	votingPower over totalVotingPower, 0 to 1
`votingPower`	Yes	this address's voting power in the validator set at height; 0 outside it
`seatWorkTotal`	No	under seat_work_power: every address's seat work over the window
`selectionRule`	Yes	top_k_by_work: the topKSize eligible miners with the most work are picked; beacon_weighted_sample: topKSize are drawn at random, weighted by work; seat_work_power: the topKSize miners with the most seat work over the window are seated, each with power in proportion to it (power moves at most 10% of the total an epoch)
`workThisEpoch`	Yes
`eligibleMiners`	Yes
`activeValidator`	Yes	in the validator set right now
`totalVotingPower`	Yes
`nextSelectionRule`	No	a different rule that applies from nextRuleFromHeight
`seatWorkThisEpoch`	No	under seat_work_power: the part of seatWork earned in this epoch
`nextRuleFromHeight`	No
`notEligibleBecause`	No	any of no_work_this_epoch, no_consensus_key, banned; under seat_work_power no_seat_work_in_window or below_minimum_share in place of no_work_this_epoch
`registeredConsensusKey`	Yes	a consensus public key is registered for this address; without one, mining never makes it a validator

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 20, 2026

addedOutput schema / properties / nextRuleFromHeight
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / nextSelectionRule

Added value: +{
+  "description": "a different rule that applies from nextRuleFromHeight",
+  "type": "string"
+}

changedOutput schema / properties / notEligibleBecause / description

Previous value: -"any of no_work_this_epoch, no_consensus_key, banned"New value: +"any of no_work_this_epoch, no_consensus_key, banned; under seat_work_power no_seat_work_in_window or below_minimum_share in place of no_work_this_epoch"

changedOutput schema / properties / onTrack / description

Previous value: -"would be picked if the epoch ended now; only ever true under top_k_by_work, since a random draw isn't known in advance"New value: +"would be picked if the epoch ended now; never true under beacon_weighted_sample, since a random draw isn't known in advance"

addedOutput schema / properties / powerShare

Added value: +{
+  "description": "votingPower over totalVotingPower, 0 to 1",
+  "type": "string"
+}

changedOutput schema / properties / rank / description

Previous value: -"1-based position among eligible miners by work; absent if not eligible"New value: +"1-based position among eligible miners by work (by seat work under seat_work_power); absent if not eligible"

addedOutput schema / properties / seatWork

Added value: +{
+  "description": "under seat_work_power: the difficulty this address's accepted submissions met over the last 3 epochs, native and merged-mined; it decides seats and power",
+  "type": "string"
+}

addedOutput schema / properties / seatWorkThisEpoch

Added value: +{
+  "description": "under seat_work_power: the part of seatWork earned in this epoch",
+  "type": "string"
+}

addedOutput schema / properties / seatWorkTotal

Added value: +{
+  "description": "under seat_work_power: every address's seat work over the window",
+  "type": "string"
+}

changedOutput schema / properties / selectionRule / description

Previous value: -"top_k_by_work: the topKSize eligible miners with the most work are picked; beacon_weighted_sample: topKSize are drawn at random, weighted by work"New value: +"top_k_by_work: the topKSize eligible miners with the most work are picked; beacon_weighted_sample: topKSize are drawn at random, weighted by work; seat_work_power: the topKSize miners with the most seat work over the window are seated, each with power in proportion to it (power moves at most 10% of the total an epoch)"

addedOutput schema / properties / totalVotingPower
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / votingPower

Added value: +{
+  "description": "this address's voting power in the validator set at height; 0 outside it",
+  "type": "integer"
+}

changedOutput schema / properties / workShare / description

Previous value: -"this address's share of all eligible work this epoch, 0 to 1; under beacon_weighted_sample it drives the odds of being drawn"New value: +"0 to 1: this address's share of all eligible work this epoch; under seat_work_power, its share of all the window's seat work, which must be at least 0.01 to qualify"

changedOutput schema / required

Previous value: -[
-  "address",
-  "height",
-  "epoch",
-  "registeredConsensusKey",
-  "banned",
-  "workThisEpoch",
-  "eligible",
-  "selectionRule",
-  "topKSize",
-  "eligibleMiners",
-  "onTrack",
-  "activeValidator",
-  "escrow"
-]New value: +[
+  "address",
+  "height",
+  "epoch",
+  "registeredConsensusKey",
+  "banned",
+  "workThisEpoch",
+  "eligible",
+  "selectionRule",
+  "topKSize",
+  "eligibleMiners",
+  "onTrack",
+  "activeValidator",
+  "votingPower",
+  "totalVotingPower",
+  "escrow"
+]

Changed1 schema field changedOct 9, 2026

changedOutput schema / properties / escrow / properties / balance / properties / asset / description

Previous value: -"AETH, or USDC (Noble's, over Aether's channel to Noble)"New value: +"AETH, or USDC (the one its owner configured: issuer and route are in origin)"

First observedOct 4, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond them: 'every field is as of one block height' (snapshot semantics), 'The address is required', 'this server holds no key', and the seat_work_power selection rule effective from block 396,000.

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?

It is front-loaded with the core question, but the long enumeration of returned fields partially duplicates what the existing output schema already provides, and the seat_work_power clause is dense jargon. Reasonably structured but with redundancy that costs it.

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?

An output schema exists, so return values need not be re-explained, yet the definition otherwise covers what is checked, the selection rule, the snapshot-at-one-block-height semantics, and the single required parameter. An agent has enough to invoke it correctly; only explicit alternative routing is missing.

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% for the single 'address' parameter, and the schema already documents the aether1... format and the 'required, server holds no key' note. The description only restates that the address is required, adding no syntax or format detail beyond the schema, so the baseline 3 is correct.

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 opens with a specific verb and resource ('Check whether an address will become a validator when this epoch ends') and then enumerates the exact fields returned, so an agent knows precisely what the tool answers. It does not need to distinguish from siblings like get_balance or get_transaction_status, which are clearly different resources, so the lack of explicit sibling differentiation is minor.

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?

The use case is implied by 'Check whether an address will become a validator when this epoch ends' and by the seat-selection rule note, so an agent can infer when this tool applies. However, there is no explicit when-to-use/when-not-to-use statement and no pointer to any alternative tool for validator/miner questions.

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

All Aether testnet wallet 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.