Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Australia · Home value index (capital cities)

australia_market_home_value_index
Read-onlyIdempotent

Our monthly home value index for the eight capital cities, for all dwellings, houses and units: index level (May 2022 = 100) plus 1-month and 12-month change. Modelled estimates.

Coverage: Eight capital cities (Sydney, Melbourne, Brisbane, Adelaide, Perth, Hobart, Darwin, Canberra), each for all dwellings, houses and units; monthly, May 2022 to September 2026 (53 months). Greater-capital-city areas; no suburb or regional series. Current to 2026-09-01. Full description, field list and method: /v1/datasets/home-value-index.

Price: 10¢ 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": "australia_market_home_value_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast period to include, same formats as `from`.
fromNoFirst period to include: 2020, 2020-Q3, 2020-07 or 2020-07-01.
fieldsNoComma-separated subset of: sydney_all, sydney_house, sydney_unit, melbourne_all, melbourne_house, melbourne_unit, brisbane_all, brisbane_house, brisbane_unit, adelaide_all, adelaide_house, adelaide_unit, perth_all, perth_house, perth_unit, hobart_all, hobart_house, hobart_unit, darwin_all, darwin_house, darwin_unit, canberra_all, canberra_house, canberra_unit, sydney_all_12m_change, sydney_house_12m_change, sydney_unit_12m_change, melbourne_all_12m_change, melbourne_house_12m_change, melbourne_unit_12m_change, brisbane_all_12m_change, brisbane_house_12m_change, brisbane_unit_12m_change, adelaide_all_12m_change, adelaide_house_12m_change, adelaide_unit_12m_change, perth_all_12m_change, perth_house_12m_change, perth_unit_12m_change, hobart_all_12m_change, hobart_house_12m_change, hobart_unit_12m_change, darwin_all_12m_change, darwin_house_12m_change, darwin_unit_12m_change, canberra_all_12m_change, canberra_house_12m_change, canberra_unit_12m_change, sydney_all_1m_change, sydney_house_1m_change, sydney_unit_1m_change, melbourne_all_1m_change, melbourne_house_1m_change, melbourne_unit_1m_change, brisbane_all_1m_change, brisbane_house_1m_change, brisbane_unit_1m_change, adelaide_all_1m_change, adelaide_house_1m_change, adelaide_unit_1m_change, perth_all_1m_change, perth_house_1m_change, perth_unit_1m_change, hobart_all_1m_change, hobart_house_1m_change, hobart_unit_1m_change, darwin_all_1m_change, darwin_house_1m_change, darwin_unit_1m_change, canberra_all_1m_change, canberra_house_1m_change, canberra_unit_1m_change. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), and the description adds genuinely new behavioral facts on top of them: the figures are modelled estimates, the data window runs May 2022 to September 2026 (53 months) and is current to 2026-09-01, and each call costs 10¢. The pricing and methodology caveats are things an agent cannot learn from the structured fields.

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 lead sentence carries the substance and the coverage block is clearly delimited, with no repetition of the long field list that already lives in the schema. The pointer to /v1/datasets/home-value-index is useful but slightly meta, and the price line could be folded into the opening, keeping it from a 5.

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?

There is no output schema, but the description tells the agent what comes back (index level plus 1-month and 12-month change per city and dwelling type), the index base, the period bounds and the geography. For a zero-required-parameter read tool, nothing needed to call it correctly is missing.

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 from/to/fields are already documented and a baseline of 3 applies. The description adds meaning beyond the schema by bounding the valid period to May 2022–September 2026 and by explaining what the field families represent (index level, 1-month change, 12-month change, all/house/unit per city).

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 verb-and-resource pair: a monthly home value index for the eight capital cities, covering all dwellings, houses and units, with index level (May 2022 = 100) and 1-month/12-month change. It also explicitly scopes out suburb and regional series, which lets an agent separate it from the suburb_market_* siblings without opening either schema.

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?

Usage context is clear because the coverage paragraph defines the geography (greater capital city only) and the granularity (monthly, no suburb or regional series), so an agent can infer when to reach for a suburb-level tool instead. It stops short of naming a specific alternative tool or calling out explicit when-not-to-use cases, so it earns 4 rather than 5.

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 toolsInspect
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