Skip to main content
Glama

Australian Economic Data (ABS, RBA & APRA)

by io.github.AnthonyPuggs

Get Economic Series

get_economic_series
Read-onlyIdempotent

Preferred analyst-facing retrieval tool for curated ABS/RBA economic concepts.

Use list_economic_concepts for discovery. Date bounds accept YYYY, YYYY-QN, YYYY-SN, YYYY-MM, or YYYY-MM-DD and are normalised to the resolved source.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoOptional analyst-friendly date bound: YYYY, YYYY-QN, YYYY-SN, YYYY-MM, or YYYY-MM-DD. Semantic retrieval normalises this to the resolved source frequency.
startNoOptional analyst-friendly date bound: YYYY, YYYY-QN, YYYY-SN, YYYY-MM, or YYYY-MM-DD. Semantic retrieval normalises this to the resolved source frequency.
last_nNoOptional limit returning only the most recent N observations per series; metadata.truncated is true when older observations were dropped.
conceptYesCurated semantic concept name.
variantNoOptional curated concept variant, such as headline, underlying, or target.
frequencyNoOptional requested frequency for a curated concept, such as monthly, quarterly, or annual.
geographyNoOptional geography selector for a curated concept, usually aus for Australia.
include_observation_dimensionsNoWhether to repeat the full dimension dict on every observation. Off by default because the same dimensions already appear on each series descriptor and are encoded in series_id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
seriesYesSeries descriptors keyed by series_id.
metadataYesSource, provenance, cache, and retrieval metadata for this response.
observationsYesLong-form observations keyed by date and series_id.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds useful behavioral context about date normalization ('normalised to the resolved source') and emphasizes it is analyst-facing, which helps set expectations beyond annotation hints.

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 two short paragraphs, front-loaded with purpose, then a discovery pointer, then the key date format detail. Every sentence adds value and there is no redundant filler.

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 the presence of a rich output schema, thorough parameter descriptions, and comprehensive annotations, the description is complete. It covers the primary use case, directs to discovery, and highlights the most critical behavioral nuance (date normalization). No significant gaps remain for an analyst-facing retrieval 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 coverage is 100% with detailed parameter descriptions (e.g., date formats, last_n truncation semantics). The description repeats some of this information (date format) but does not add meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 identifies the tool as the 'Preferred analyst-facing retrieval tool for curated ABS/RBA economic concepts', specifying both the action (retrieval) and the resource (curated concepts). It distinguishes itself from siblings by positioning it as preferred and referencing discovery via list_economic_concepts.

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 explicitly directs users to 'Use list_economic_concepts for discovery', providing an alternative for a related task. The phrase 'Preferred analyst-facing retrieval tool' implies when to choose this tool over others, though it doesn't detail when not to use tools like get_derived_series or get_abs_data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Australian Economic Data (ABS, RBA & APRA) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools have clear source or function boundaries (ABS, RBA, APRA, derived series, curated concepts, discovery). However, get_derived_series and get_economic_series both retrieve time-series data and could be confused; list_catalogue and search_datasets also overlap in discovery. The descriptions help, but these pairs require careful reading.

Naming Consistency5/5

All tools follow a consistent lowercase verb_noun pattern with underscores (describe_, get_, list_, search_). Verbs are used predictably: get for retrieval, list for enumeration, search for discovery. No mixed conventions or camelCase.

Tool Count4/5

14 tools is on the higher end but appropriate for a multi-source economic data API covering ABS, RBA, and APRA. The inclusion of a deprecated alias (list_rba_tables) adds slight redundancy, but the overall count is justified by distinct operations.

Completeness4/5

The surface covers discovery (search_datasets, list_catalogue), metadata (describe_dataset, structure), retrieval (source-specific and curated), and convenience wrappers (latest/top observations). Minor gaps include lack of a unified structure tool for RBA/APRA and no bulk download option, but core read-only workflows are well covered.

Resources