Skip to main content
Glama
Bigred97

Australian Prudential Regulation Authority

get_data

Retrieve curated APRA data on banks, super funds, and insurers. Filter by institution, measures, and time period to get observations.

Instructions

Query a curated APRA dataset and return observations.

Examples: # CBA's CET1 ratio over time resp = await get_data( "ADI_KEY_STATS", filters={"institution": "cba"}, measures="cet1_ratio", )

# Major banks' total capital, last 5 quarters
resp = await get_data(
    "ADI_KEY_STATS",
    filters={"sector": "major_banks"},
    measures="total_capital",
    start_period="2024-01-01",
)

# Total industry gross written premium (general insurance)
resp = await get_data(
    "INSURANCE_GENERAL",
    filters={"data_item": "Gross written premium",
             "industry_segment": "total_industry"},
)

# AustralianSuper member account counts
resp = await get_data(
    "SUPER_FUND_LEVEL",
    filters={"fund_name": "australian_super"},
    measures=["total_member_accounts", "total_members_benefits"],
)

Returns: DataResponse with records (or csv), unit, period bounds, row_count, source URL, the actual download_url used, optional framework info (insurance only), and CC-BY 3.0 AU attribution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataset_idYesCurated dataset ID. Use search_datasets() / list_curated().
filtersNoDimension filters. Keys are plain-English aliases from the dataset's describe_dataset response. Values are matched against the source data; pass a list to OR across values. Permissive dimensions (e.g. institution, fund_name, data_item) accept any string — including substring search via trailing '*' (e.g. {'institution': 'macquarie*'}).
measuresNoWhich measure(s) to return. Plain-English keys from describe_dataset. Omit to return all measures. For long-format datasets (insurance), the single measure is 'value' and the semantic metric lives in the 'data_item' dimension filter.
start_periodNoInclusive start period. Format: 'YYYY-MM-DD' (e.g. '2024-01-01'), 'YYYY-Qx' (e.g. '2024-Q1'), or 'YYYY'. Matched against the dataset's period_column (quarter-end date).
end_periodNoInclusive end period. Same format as start_period.
formatNoResponse shape. 'records' (default): flat list of observations. 'series': grouped by measure. 'csv': pandas CSV string in `csv` field.records

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataset_idYes
dataset_nameYes
queryNo
periodNo
unitNo
row_countNo
recordsNo
csvNo
sourceNoAustralian Prudential Regulation Authority
attributionNoSource: Australian Prudential Regulation Authority. Licensed under Creative Commons Attribution 3.0 Australia (https://creativecommons.org/licenses/by/3.0/au/).
retrieved_atYes
apra_urlYes
download_urlNo
frameworkNo
staleNo
stale_reasonNo
server_versionNo
Behavior4/5

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

No annotations provided, so description carries full burden. It details return format (records, series, csv) and output fields like source URL and attribution. Lacks rate limits or authentication, but as a query tool, behavior is well-described.

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?

Description is concise (~20 lines) with a clear purpose statement, followed by diverse examples, and a return summary. Every sentence adds value, no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 6 parameters, 100% schema coverage, and an output schema, the description covers all necessary context: dataset selection, filters with advanced features, period formats, and output options. Examples cover major use cases.

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% with descriptions for all parameters. Description adds valuable examples demonstrating complex filters, wildcards, and usage of optional parameters, going beyond schema alone.

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?

Description explicitly states 'Query a curated APRA dataset and return observations.' Clear verb+resource. Examples enhance clarity but no explicit differentiation from siblings like describe_dataset.

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?

Examples show common usage patterns, implying when to use the tool. No explicit instructions on when not to use or alternatives, leaving agent to infer from context.

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/apra-mcp'

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