Skip to main content
Glama
Bigred97

Australian Prudential Regulation Authority

latest

Get the most recent data point per measure from a dataset, answering current-value questions like 'What is CBA's CET1 ratio?'.

Instructions

Return the most recent observation per measure for a dataset.

Trims to the single latest period per measure across the filtered slice — useful for "what's CBA's current CET1?" style questions without having to think about start_period. Wide-layout entity-level datasets (INSURANCE_GENERAL etc.) are capped at limit rows.

Examples: # Latest CBA capital ratios resp = await latest("ADI_KEY_STATS", filters={"institution": "cba"})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum rows to return. Wide-layout entity-level datasets (INSURANCE_GENERAL ~2,000 rows per quarter) can blow an agent's context window without a cap. Pass filters to narrow to one entity; raise `limit` only if you genuinely need a bulk dump. Truncated responses set DataResponse.truncated_at to the original row count.
filtersNoSame filter shape as get_data. Useful for narrowing to one entity.
measuresNoSame as get_data.
dataset_idYesCurated dataset ID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
csvNo
unitNo
queryNo
staleNo
periodNo
sourceNoAustralian Prudential Regulation Authority
recordsNo
apra_urlYesClick-through URL for this dataset's source page. apra-mcp legacy name — prefer source_url (canonical) for new code. Both fields are populated identically.
frameworkNo
row_countNo
dataset_idYes
source_urlYesCanonical click-through URL. Same value as apra_url; both populated for backward compat.
attributionNoSource: Australian Prudential Regulation Authority. Licensed under Creative Commons Attribution 3.0 Australia (https://creativecommons.org/licenses/by/3.0/au/).
dataset_nameYes
download_urlNo
retrieved_atYes
stale_reasonNo
truncated_atNo
server_versionNo
Behavior5/5

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

No annotations provided; the description fully explains the trimming logic, row cap for wide-layout datasets, and truncated response indicator, exceeding basic expectations.

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?

Every sentence adds value: purpose, trimming logic, row cap note, and example. No redundancy, front-loaded with core action.

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?

Covers purpose, use case, behavior, and example adequately. With an output schema existing, return values need no further explanation. Minor improvement could include error handling, but not essential.

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 baseline is 3. The description adds context for limit (capping, truncation), filters (same shape as get_data), and measures (referencing get_data), raising it to 4.

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 explicitly states 'Return the most recent observation per measure for a dataset.' with examples like 'Latest CBA capital ratios,' clearly distinguishing it from siblings such as get_data (raw data) and top_n (top values).

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 advises use for 'current value' queries without specifying periods, but does not explicitly exclude alternatives or list when not to use it.

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