Skip to main content
Glama
Bigred97

Reserve Bank of Australia

latest

Retrieve the current value of any Reserve Bank of Australia indicator, such as the cash rate or exchange rates, with a single call.

Instructions

Return the most recent observation for each series in an RBA F-table.

Wraps get_data with last_n=1 (and a shorter cache TTL). Use this for "what's the current X?" questions — it's a cheap, fast call.

Examples: # Current cash rate target resp = await latest("F1.1", series="cash_rate_target") # → resp.records[0]: period='2026-05-06', value=3.85, unit='Per cent per annum'

# All AUD FX rates in one call (curated dashboard pattern)
resp = await latest("F11.1")
# → resp.records: latest aud_usd, aud_eur, aud_jpy, aud_cny, etc.

# Latest standard variable mortgage rate
resp = await latest("F6", series="housing_standard_variable")

When to use: - You want the current value of an RBA indicator - You want a current-snapshot of multiple series in one call (e.g. latest("F11.1") returns every FX rate) - You want sub-50ms warm-cache latency for chat integration

Returns: DataResponse with one most-recent observation per series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
table_idYesRBA F-table ID. Use search_tables() to discover.
seriesNoWhich series to return. For curated tables: plain-English keys. Pass None (default) to get the latest observation for every curated series in the table — useful for dashboards.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
table_idYes
table_nameYes
queryNo
periodNo
unitNo
recordsNo
csvNo
sourceNoReserve Bank of Australia
attributionNoData sourced from the Reserve Bank of Australia and licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). https://www.rba.gov.au/copyright/
retrieved_atYes
rba_urlYes
server_versionNo
Behavior4/5

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

With no annotations, the description carries full burden. It reveals the tool is a wrapper with last_n=1 and shorter cache TTL, mentions sub-50ms latency, and provides return structure via examples. Minor omission of error handling or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with four short paragraphs, each sentence adding value. It is front-loaded with the purpose and efficiently covers usage, examples, and return value.

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 simple wrapper tool with a clear output schema, the description covers purpose, usage, parameters, and return format. It could mention error handling for invalid table IDs, but is otherwise complete.

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 description coverage is 100%, so baseline is 3. The description adds significant value with examples of usage, explains the effect of passing None for series, and shows the return structure, going beyond the schema.

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 returns the most recent observation for each series in an RBA F-table. It distinguishes itself from siblings by noting it wraps get_data with last_n=1 and is intended for current-value queries.

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 includes a 'When to use' section with three clear bullet points explaining appropriate contexts. It implies when not to use (historical data) by referencing it wraps get_data, but does not explicitly list alternatives or exclusions.

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/Bigred97/rba-mcp'

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