Skip to main content
Glama
Bigred97

Australian Bureau of Statistics

search_datasets

Search Australian Bureau of Statistics datasets by topic. Returns ranked results with curated dataflows prioritized for common queries.

Instructions

Fuzzy-search ABS dataflow names, descriptions, and keywords.

Use this when you don't know the exact dataset ID. The 10 curated dataflows (LF, CPI, ANA_AGG, etc.) get a relevance boost so common queries like "unemployment" or "gdp" return the right dataset at rank #1 — not one of ABS's 800+ census tables that mention these keywords incidentally.

Examples: # Discover which dataflow answers "what's NSW unemployment?" results = await search_datasets("unemployment") # → [{id: 'LF', name: 'Labour Force', is_curated: True}, ...]

# Broader topic exploration
results = await search_datasets("housing", limit=5)
# → top 5 housing-related dataflows, curated first

When to use: - You have a natural-language question and need to identify the dataset - You want to discover what ABS publishes on a topic - You're not sure if a topic has a plain-English (curated) mapping yet

Returns: List of DatasetSummary (id, name, description, is_curated), ranked by relevance. Curated dataflows surface above raw SDMX dataflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return, ranked by relevance. Curated dataflows get a +25 score bonus so they surface above ABS's ~800 census tables for common queries.
queryYesFree-text search query. Matches against dataflow IDs, names, descriptions, and each curated YAML's search_keywords. Case-insensitive.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description fully explains behavior: fuzzy matching, boosted curated dataflows, relevance ranking, and return type. Minor omission: does not clarify if authentication or side effects exist, but that's acceptable for a search 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: purpose first, then usage, examples, when-to-use, returns. It is front-loaded and each sentence adds value. A minor redundancy exists between the first 'Use this when...' and the 'When to use' list.

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 simplicity (2 params) and the presence of an output schema, the description covers all needed aspects: functionality, usage context, behavioral details, examples, and return type. It is complete for an agent to use correctly.

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 value by explaining the +25 score bonus for curated dataflows and providing examples, exceeding what the schema alone offers.

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 'Fuzzy-search ABS dataflow names, descriptions, and keywords.' It specifies the verb (fuzzy-search) and resources (dataflow names, descriptions, keywords), and differentiates from sibling tools like describe_dataset and get_data by noting it's for when you don't know the exact ID.

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 says 'Use this when you don't know the exact dataset ID' and provides a list of when-to-use scenarios. However, it does not explicitly say when not to use it or contrast with specific sibling tools like list_curated.

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