Skip to main content
Glama
Bigred97

Australian Bureau of Statistics

describe_dataset

Discover valid filter dimensions, value codes, and source URL for any ABS dataflow. Check if a dataflow supports plain-English values or raw SDMX codes before querying.

Instructions

Describe an ABS dataflow's filter dimensions, value codes, and source.

For curated dataflows (LF, CPI, ANA_AGG, AWE, BA_GCCSA, ERP_Q, JV, LEND_HOUSING, WPI, ABS_ANNUAL_ERP_ASGS2021), returns plain-English dimension names + curated value keys + the ABS source URL.

For other dataflows (~1,200 in total), returns raw SDMX dimensions and codelists translated to the same response shape — pass raw SDMX codes to get_data when querying these.

Examples: # Curated path — plain-English values detail = await describe_dataset("LF") # detail.dimensions = [{'name': 'region', 'values': [{'key': 'nsw', # 'sdmx_code': '1'}, {'key': 'vic', 'sdmx_code': '2'}, ...]}, ...]

# Raw path — full SDMX codelist
detail = await describe_dataset("ALC")  # Apparent Consumption of Alcohol
# detail.is_curated == False; values are raw SDMX codes

When to use: - Before calling get_data on an unfamiliar dataflow — to discover valid filter dim names and value keys - To get the canonical source URL on the ABS site - To see whether a dataflow is curated (plain-English) or raw SDMX

Returns: DatasetDetail with id, name, description, is_curated flag, the list of filter dimensions (name, sdmx_id, values), and abs_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataset_idYesABS dataflow ID. Use search_datasets to discover, or list_curated to enumerate the 10 dataflows with plain-English support. Case-insensitive — 'lf', 'LF', and ' LF ' all resolve to 'LF'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameYes
abs_urlYes
dimensionsYes
is_curatedYes
descriptionYes
hidden_defaultsNo
Behavior4/5

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

Since no annotations are provided, the description covers key behaviors: curated vs. raw paths, case-insensitivity, and whitespace trimming. It lacks discussion of side effects or authorization, but as a metadata-read operation, these are implicitly safe.

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 sections, examples, and bullet points, making it easy to scan. While slightly verbose, it remains clear and front-loaded with the core purpose.

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 tool's single parameter and the presence of an output schema, the description comprehensively covers behavior, return shape, and usage scenarios. It is complete for an effective tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, yet the description adds significant value: it explains case-insensitivity, trimming, and how to discover valid IDs via search_datasets or list_curated. Examples reinforce correct usage.

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 states the tool's purpose: describing an ABS dataflow's filter dimensions, value codes, and source. It distinguishes between curated and raw dataflows, providing specific examples (LF, CPI, etc.) and contrasting with sibling tools like get_data and search_datasets.

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 explicitly tells when to use the tool, e.g., before calling get_data on an unfamiliar dataflow or to get the source URL. It does not provide explicit 'when not to use' guidance or direct comparisons to alternatives, but the context is clear.

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

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