AusEcon MCP for ABS | RBA | APRA data

Search Datasets

search_datasets

Read-onlyIdempotent

Search ABS, RBA, and APRA economic datasets by keyword, with optional source filter for targeted results.

Instructions

Search curated ABS, RBA, and APRA economic datasets.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_datasets"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Discovery query text.
`source`	No	Optional source filter. Use abs for Australian Bureau of Statistics, rba for Reserve Bank of Australia, or apra for Australian Prudential Regulation Authority.

Output Schema

Name	Required	Description	Default
`result`	Yes	Ranked ABS, RBA, and APRA catalogue search results.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 31, 2026

TDQS

A3.6/5.0

Behavior3/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 covered. The description adds minimal context like 'curated' suggesting a limited dataset set, but doesn't describe result behavior, pagination, or matching semantics. No contradiction with annotations.

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 a single sentence that front-loads the action ('Search') and scope ('curated ABS, RBA, and APRA economic datasets'). Every word earns its place with no redundancy.

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?

For a simple search tool, the description is largely sufficient given that annotations cover safety and the output schema covers return values. However, it omits details about search behavior (e.g., exact vs. fuzzy matching) and could briefly indicate when to prefer this over list_catalogue, which would improve completeness.

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?

The input schema has 100% description coverage for both parameters, with query described as 'Discovery query text' and source explaining each enum value. The description adds no additional parameter semantics beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches curated economic datasets from ABS, RBA, and APRA, using a specific verb and resource scope. While it doesn't explicitly contrast with sibling tools, the 'Search' verb and the named sources distinguish it sufficiently from retrieval tools like get_abs_data or list_catalogue.

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?

There is no explicit guidance on when to use this tool versus alternatives. The description implies it is for searching datasets by query, but does not mention when to use list_catalogue or how it differs from specific data retrieval tools.

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

Deploy Server