Microburbs Australian Property Data

Economics · List economic series

economics_series

Read-onlyIdempotent

Every economic series we hold — national statistics and the RBA — with its latest value. Use it to find a series_id, then fetch the history from /economics/series/{series_id}.

Datasets: cpi (25 items incl. rents and new dwellings, 8 capitals + national, monthly and quarterly), cash-rate, mortgage-rates (banks' indicator rates), wpi (wages), building-approvals (states + capital cities), housing-lending (owner-occupier, investor, first home buyers), population, labour-force and dwelling-transfers (median prices and counts by capital city).

Price: 1¢ per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "economics_series"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`query`	No	Words that must all appear in the series id or title.
`offset`	No
`region`	No	australia, a state (nsw, vic…), a capital city (sydney…) or greater-sydney style GCCSA.
`dataset`	No	One of: cpi, cash-rate, mortgage-rates, wpi, building-approvals, housing-lending, population, labour-force, dwelling-transfers.
`frequency`	No	monthly, quarterly or event.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description adds useful behavioral context by disclosing the 1¢ per-call price and stating that results include latest values, though it does not describe pagination or ordering behavior.

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 front-loaded with purpose and usage, then provides a dataset catalogue that earns its space by helping agents choose the right dataset. The dataset list is lengthy but relevant, and the price disclosure is clearly placed at the end.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter listing tool with no output schema, the description explains the discovery workflow, dataset coverage, and pricing, but it does not describe the return shape beyond latest values or explain pagination. It is adequate but leaves some operational details to be inferred from the schema.

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 67%, and the description adds meaningful semantic detail for the `dataset` parameter by expanding what each dataset contains, such as CPI scope and housing-lending categories. However, it does not add guidance for `limit`, `offset`, `query`, `region`, or `frequency` beyond what the schema already provides.

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 states a specific resource and scope: every economic series held, including national statistics and RBA series, with latest values. It also distinguishes this discovery/list tool from the history-fetching sibling by explaining that it returns a `series_id` for use with `/economics/series/{series_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?

It gives clear usage guidance: use this tool to find a `series_id`, then fetch history from the series-history endpoint. It does not explicitly compare against all nearby siblings such as `economics_cpi_latest` or `economics_cash_rate`, but the primary workflow and alternative are clear.

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

All Microburbs Australian Property Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?