Skip to main content
Glama

get_data

Retrieve curated ATO and ACNC data on personal tax, company tax, charity finances, and super contributions. Filter by location, time period, and measure to get targeted observations.

Instructions

Query a curated ATO/ACNC dataset and return observations.

Examples: # Median taxable income in postcode 2000 (Sydney CBD), 2022-23 resp = await get_data( "IND_POSTCODE_MEDIAN", filters={"state": "nsw", "postcode": "2000"}, measures="median_taxable_income_2022_23", )

# All registered charities in NSW with size = "large"
resp = await get_data(
    "ACNC_REGISTER",
    filters={"state": "NSW", "charity_size": "Large"},
    measures=["total_gross_income", "total_employees"],
)

# 500 ACNC charity financial records (huge dataset — cap to fit context)
resp = await get_data(
    "ACNC_AIS_FINANCIALS",
    filters={"state": "NSW"},
    limit=500,
)

# 2023-24 corporate tax payable for entities with total income > $1B
resp = await get_data("CORP_TRANSPARENCY", filters={"income_year": "2023-24"})

Returns: DataResponse with records (or csv), unit, period bounds, row_count, source URL, and CC-BY attribution. truncated_at is set when the underlying slice was larger than limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoOptional cap on number of records returned. Useful for register-shaped datasets where a slice can still be very large (ACNC_AIS_FINANCIALS = ~50k charities × 16 measures = 800k+ records; ACNC_REGISTER = ~65k charities). Without a cap the response can blow an agent's context window. Truncated responses set DataResponse.truncated_at to the original row count. Default None = no cap (subject to the portfolio-wide 100k hard ceiling for pathological cases).
formatNoResponse shape. 'records' (default): flat list of observations. 'series': grouped by measure. 'csv': pandas CSV string in `csv` field.records
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. Examples: {'state': 'nsw'}, {'postcode': '2000'}, {'industry_broad': ['A', 'B']}.
measuresNoWhich measure(s) to return. Plain-English keys from describe_dataset. Omit to return all measures.
dataset_idYesCurated dataset ID. Use search_datasets() / list_curated().
end_periodNoInclusive end period. Same format as start_period.
start_periodNoInclusive start period for transposed time-series datasets (GST_MONTHLY etc). Ignored for wide single-year tables. Format: 'YYYY' or 'YYYY-MM' or ATO FY 'YYYY-YY'. Bare int years like 2020 are coerced to '2020' automatically.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
csvNo
unitNo
queryNo
staleNo
periodNo
sourceNoAustralian Taxation Office
ato_urlYesClick-through URL for this dataset's source page. ato-mcp legacy name — prefer source_url (canonical) for new code. Both fields are populated identically.
recordsNo
row_countNo
dataset_idYes
source_urlYesCanonical click-through URL. Same value as ato_url; both populated for backward compat.
attributionNoData sourced from the Australian Taxation Office (and, for charity data, the Australian Charities and Not-for-profits Commission) via data.gov.au. Licensed under Creative Commons Attribution 3.0 Australia (CC BY 3.0 AU). https://creativecommons.org/licenses/by/3.0/au/
dataset_nameYes
retrieved_atYes
stale_reasonNo
truncated_atNo
server_versionNo
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a DataResponse with records/csv, unit, period bounds, row_count, source URL, and CC-BY attribution. It also mentions truncation behavior with 'truncated_at'. However, it does not address error handling, rate limits, or authentication requirements, which are minor gaps for a read-only query tool.

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

Conciseness4/5

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

The description is well-structured with a clear purpose statement, multiple examples with comments, and a return value summary. It is front-loaded with the core purpose. While slightly lengthy, each section (examples, return description) earns its place without extraneous content.

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?

Given 7 parameters, 100% schema coverage, and an output schema (mentioned in return description), the tool description is complete. It explains how to discover dataset IDs using 'search_datasets() / list_curated()', and describes the return structure. The examples cover common use cases (filtering, limiting, choosing format). Minor omission: no discussion of pagination or handling large responses beyond truncation.

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 description coverage is 100%, so the schema already documents all 7 parameters well. The description adds value through examples that illustrate parameter usage (e.g., filters, measures, limit) but does not introduce new semantic information beyond the schema examples. Baseline 3 is appropriate as the description complements but does not exceed the schema's coverage.

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 'Query a curated ATO/ACNC dataset and return observations.' The verb 'Query' and resource 'curated dataset' are specific. Multiple examples demonstrate usage with different datasets and parameters, clearly distinguishing it from sibling tools like 'describe_dataset' (describes schema) and 'search_datasets' (finds datasets).

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?

The description provides examples that imply usage scenarios (e.g., filtering by state, limiting records) but does not explicitly state when to use this tool versus alternatives. No exclusions or when-not-to-use guidance is given, leaving the agent to infer context from examples alone.

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

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