Reserve Bank of Australia
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_tablesA | Fuzzy-search RBA F-tables by name and topic. Use this when you don't know the exact table ID. The 5 curated F-tables (F1.1, F4, F6, F11, F11.1) cover the most-asked indicators: cash rate, money-market rates, household lending rates, FX rates. Examples: # Find the F-table that publishes the cash rate results = await search_tables("cash rate") # → [{id: 'F1.1', name: 'Interest Rates and Yields - Money Market', ...}] When to use: - You have a natural-language question and need to identify the table - You want to discover what RBA publishes on a topic - You're enumerating the F-table catalog programmatically Returns: List of TableSummary (id, name, frequency, description), ranked by relevance. Curated tables surface above the rest. |
| describe_tableA | Describe an RBA F-table's series, units, and frequency. For curated F-tables (F1.1, F4, F6, F11, F11.1), returns plain-English series keys (like 'cash_rate_target', 'aud_usd') with descriptions and units. For other F-tables, fetches the CSV and returns the raw RBA series IDs from the header along with start dates. Examples: # Curated table — plain-English keys detail = await describe_table("F1.1") # detail.series[0]: key='cash_rate_target', series_id='FIRMMCRT', # unit='Per cent per annum', frequency='Daily' When to use: - Before calling get_data on a new table — to discover valid series keys - To get the canonical RBA source URL for citation - To distinguish curated (plain-English) tables from raw F-tables Returns: TableDetail with id, name, description, is_curated flag, frequency, list of SeriesDetail (key, series_id, description, unit), and rba_url. |
| get_dataA | Query an RBA F-table and return observations. 2023-01-01,..." |
| latestA | 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 (explicit) resp = await latest("F1.1", series="cash_rate_target") # → resp.records[0]: period='2026-05-06', value=3.85, unit='Per cent per annum' When to use: - You want the current value of an RBA indicator - You want a current-snapshot of multiple series in one call (pass an explicit list — e.g. all FX rates) - You want sub-50ms warm-cache latency for chat integration Returns: DataResponse with one most-recent observation per requested series. |
| list_curatedA | List the 5 RBA F-table IDs with hand-curated plain-English support. These are the tables where get_data and latest accept plain-English series keys (like 'cash_rate_target', 'aud_usd'). Other F-tables are still queryable via raw RBA series IDs. The 5 curated F-tables: - F1.1 — Interest Rates and Yields: Money Market (incl. cash rate target) - F4 — Money Market Operations - F6 — Housing Lending Rates (standard variable, fixed, etc.) - F11 — Exchange Rates (AUD vs major currencies, daily) - F11.1 — Exchange Rate Indices (TWI, real TWI) Example: ids = list_curated() # → ['F1.1', 'F11', 'F11.1', 'F4', 'F6'] When to use: - You want to know which tables have plain-English support - You're building a UI / agent that needs the supported set up front - You want to plan which F-tables to call without inspecting each Returns: Sorted list of F-table IDs. Always 5 entries today. |
| release_calendarA | Upcoming RBA publication schedule (data + statements + events). Scrapes https://www.rba.gov.au/schedules-events/ and merges the two
schedule tables into a single chronological feed. Each entry reports
Event types:
- Returns the same envelope shape as Cached at 24h TTL with stale-fallback on 5xx (per portfolio graceful-degradation policy). The gateway should poll on its own schedule rather than hitting the live HTML. Examples: cal = await release_calendar(7) for r in cal.releases: print(r.release_at, r.event_type, r.title, r.publication_id) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool serves a clearly distinct purpose: describe_table provides metadata, get_data retrieves time series, latest is a specialized wrapper for current values, list_curated enumerates tables with plain-English support, release_calendar gives publication schedules, and search_tables helps discover tables. The only potential overlap (get_data vs latest) is explicitly addressed with documentation clarifying use cases.
All tool names use snake_case with a consistent verb_noun pattern (describe_table, get_data, list_curated, release_calendar, search_tables). Even 'latest' follows the pattern implied by 'get_data' as a convenience alias. No mixing of conventions or inconsistent verb styles.
Six tools is well-scoped for an RBA data server, covering metadata discovery (describe_table, list_curated, search_tables), data retrieval (get_data, latest), and schedule information (release_calendar). This is neither too sparse nor too heavy for the domain.
The tool surface covers the essential lifecycle: discover tables (search_tables, list_curated), inspect structure (describe_table), and retrieve data (get_data, latest) plus schedule awareness (release_calendar). Minor gaps exist (e.g., no direct bulk download or advanced filtering), but the core workflows are supported without dead ends.