Retirement Wealth Data

Get a figure

get_figure

Read-onlyIdempotent

Gets one Australian retirement figure by an id from search_figures. Returns the value recorded for a date (as_at, or today in Sydney), the date it applies from and what that date means, conditions, exceptions, the official source by name, the date last checked and a citation of the figure's Retirement Wealth page. Values set by law but not yet in force are listed under upcoming. No value is returned for a date before the earliest recorded value, after today, or from the start of a value set by law not yet confirmed in force.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The figure id, such as concessional_cap. search_figures returns ids.
`as_at`	No	A date, as YYYY-MM-DD. Leave it out for today's date in Sydney.
`include_history`	No	Also return the earlier recorded values, newest first. Default false.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`kind`	Yes
`note`	Yes
`page`	Yes	The figure's Retirement Wealth page: its value, conditions, change history and a link to its official source.
`unit`	Yes
`as_at`	Yes	The date the value was looked up for.
`label`	Yes
`notes`	Yes
`ratio`	Yes	For rates, the same value as a plain ratio: 3.75 per cent is 0.0375. Otherwise null.
`scope`	Yes	What this site does and does not provide.
`today`	Yes	Today's date in Sydney when the request was answered.
`value`	Yes
`resets`	Yes
`source`	Yes	The official source, by publisher and title. Its address is on the figure's Retirement Wealth page.
`status`	Yes	in_force: the registry's current value. superseded: an earlier value.
`caveats`	Yes
`cite_as`	Yes	A citation line: the value, its date, the official source by name, the date it was last checked and the figure's Retirement Wealth page.
`concept`	Yes
`history`	No	Recorded values, newest first.
`category`	Yes
`citation`	Yes	The figure's Retirement Wealth page, as an address and a title.
`recorded`	Yes	True when a value is recorded for as_at. False when it is not: the value fields are then null and note says why.
`upcoming`	Yes	Values set by law that are not the current value here: for a later date, or not yet confirmed in force.
`data_hash`	Yes
`former_id`	Yes	Set when the id asked for is an earlier id of this figure.
`applies_by`	Yes
`conditions`	Yes
`derivation`	Yes	The calculation that links this figure to the figures it is worked out from, or null.
`dimensions`	Yes
`exceptions`	Yes	Exceptions. One marked modelled: false is not built into any calculation on this site.
`review_due`	Yes	due: true when the figure's first scheduled review day after it was last checked (from) is on or before as_at, today in Sydney: the figure has not been checked against its source since that review. note says so in words when due is true. from is null for a figure with no fixed review days.
`value_notes`	Yes
`data_release`	Yes	The number of the data release these values come from.
`effective_to`	Yes	The last day the value applies: the day before the next recorded value starts. Null when no later value is recorded, or when the end is not recorded.
`history_note`	No
`review_dates`	Yes
`verification`	Yes	How the value was verified and the date it was last checked against its source.
`display_value`	Yes
`history_total`	No
`category_label`	Yes
`effective_from`	Yes	The date the value applies from. effective_from_basis says what the date means.
`earliest_recorded`	Yes	The earliest date for which a value of this figure is held.
`history_truncated`	No	True when history was cut short to keep the response small.
`effective_from_basis`	Yes	value: the day this value started. provision: the day the current rule started; the number itself is older. as_at: a day the official source shows the value in force; the day it started is not recorded.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 19, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

changedOutput schema / properties / applies_by / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "selector": {
-        "type": "string"
-      },
-      "text": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "selector",
-      "text"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "selector": {
+        "type": "string"
+      },
+      "text": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "selector",
+      "text"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / caveats / items / additionalProperties
```
Previous value: -falseNew value: +{}
```
changedOutput schema / properties / citation / additionalProperties
```
Previous value: -falseNew value: +{}
```
changedOutput schema / properties / conditions / items / additionalProperties
```
Previous value: -falseNew value: +{}
```
changedOutput schema / properties / exceptions / items / additionalProperties
```
Previous value: -falseNew value: +{}
```
changedOutput schema / properties / history / items / additionalProperties
```
Previous value: -falseNew value: +{}
```
changedOutput schema / properties / review_due / additionalProperties
```
Previous value: -falseNew value: +{}
```

changedOutput schema / properties / source / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "publisher": {
-        "type": "string"
-      },
-      "title": {
-        "type": "string"
-      },
-      "type": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "title",
-      "publisher",
-      "type"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "publisher": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "title",
+      "publisher",
+      "type"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / unit / additionalProperties
```
Previous value: -falseNew value: +{}
```
changedOutput schema / properties / upcoming / items / additionalProperties
```
Previous value: -falseNew value: +{}
```

changedOutput schema / properties / verification / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "checked_on": {
-        "type": "string"
-      },
-      "status": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "status",
-      "checked_on"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "checked_on": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "status",
+      "checked_on"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 19, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behaviour, so the bar is lower; the description still adds real behavioural detail by naming the three cases that yield no value (before the earliest recorded value, after today, and values set by law but not yet in force, surfaced under 'upcoming'). However, a large part of the text merely enumerates return fields that the output schema already carries.

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 first sentence is well front-loaded, but the rest is one long run-on sentence enumerating returned fields, much of which duplicates the output schema rather than earning its place. Size is defensible for a data-lookup tool but not tight.

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?

With an output schema present the return-value listing is not strictly needed, and annotations cover safety; the description's genuine contribution is the empty-result semantics and the source/citation context, which completes the picture for a three-parameter lookup tool.

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%: the id example (concessional_cap), the as_at YYYY-MM-DD format with Sydney default, and include_history's default are all documented in the schema. The description adds no syntax or format detail beyond it, so the baseline 3 applies.

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 opening sentence states a specific verb and resource ('Gets one Australian retirement figure') and pins the id's origin to the sibling tool search_figures, making it distinguishable from list_categories, list_changes and search_figures at a glance.

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 clearly routes the agent to search_figures as the way to obtain a valid id and explains the conditions under which no value comes back, which is effectively a when-not-to-expect-results rule. It does not explicitly contrast itself with list_changes or list_categories, so it falls short of full alternative routing.

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?