Retirement Wealth Data

List changes

list_changes

Read-onlyIdempotent

Lists what this site has changed in its published Australian retirement figures since a date, such as new or corrected values, earlier values added and figures added or renamed. Newest first. since filters on recorded_on, the date this site recorded the change, in Sydney. effective_from is the date the changed value applies from, where the change has one. A value can be recorded long after it began to apply.

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": {
      "since": "<since>"
    },
    "name": "list_changes"
  }
}

Input Schema

Name	Required	Description
`limit`	No	The most changes to return. Default 25, maximum 100.
`since`	Yes	Return changes recorded on or after this date, as YYYY-MM-DD. This is the date the change was recorded, not the date a value applies from.
`types`	No	Only these kinds of change.
`figure_id`	No	Only changes to this figure.

Output Schema

Name	Required	Description
`note`	Yes
`count`	Yes
`scope`	Yes	What this site does and does not provide.
`since`	Yes
`total`	Yes	How many items matched.
`types`	Yes
`events`	Yes
`changes`	Yes
`data_hash`	Yes
`figure_id`	Yes
`truncated`	Yes	True when there are more items than this result holds.
`data_release`	Yes	The number of the data release these values come from.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 19, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- changedOutput schema / properties / events / items / additionalProperties
```
Previous value: -falseNew value: +{}
```
First observedOct 19, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With readOnlyHint, idempotentHint, and destructiveHint already declaring the safety profile, the description still adds behavioral value: 'Newest first' ordering, the definition of 'since' as the recorded date in Sydney, and the caveat that a value can be recorded long after it began to apply. It does not mention pagination beyond the limit param, but the added ordering and time-semantics context go meaningfully beyond the annotations.

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 core purpose and ordering are front-loaded in the first two sentences, with the date semantics following. Most sentences earn their place, though the effective_from/applies-from discussion drifts into return-value territory and is slightly redundant for selecting and invoking the tool.

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 documented; the description nonetheless explains effective_from, which overlaps with the output contract. For a read-only list tool with a well-documented schema and annotations, the definition is essentially complete for correct invocation, with only minor redundancy.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema lacks: 'since' is clarified as the recorded date in Sydney (timezone absent from the schema), and the recorded_on vs applies-from distinction disambiguates the filter. The mention of effective_from is an output field rather than a parameter, which is a slight mismatch but it aids interpretation.

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 verb and resource ('lists what this site has changed in its published Australian retirement figures') with an explicit scope ('since a date') and enumerates the change kinds returned. This clearly separates it from siblings like get_figure and search_figures, which fetch current values rather than a change log.

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 implied by the change-log framing and the 'since a date' constraint, but there is no explicit when-to-use vs when-to-use-alternatives guidance, no exclusions, and no routing to siblings. Minimum viable rather than helpful.

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

All Retirement Wealth Data 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?