Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Dwelling structure

suburbs_area_stats_dwelling_structure
Read-onlyIdempotent

What kind of homes an area is made of: separate houses, semi-detached and townhouses, flats by height of block, and other dwellings, plus how many homes stood empty, for every suburb and council area.

Coverage: About 11,500 suburbs and localities and 545 council areas across Australia, in all states and territories (areas with too few people or homes for reliable figures are left out); one snapshot at 10 August 2021. Current to 2021-08-10. Full description, field list and method: /v1/datasets/dwelling-structure.

Price: 5¢ per call.

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": {
      "suburb_name": "<suburb_name>"
    },
    "name": "suburbs_area_stats_dwelling_structure"
  }
}

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: total_occupied_dwellings, separate_house_count, separate_house_pct, semi_detached_count, semi_detached_pct, semi_detached_one_storey_count, semi_detached_one_storey_pct, semi_detached_two_plus_storeys_count, semi_detached_two_plus_storeys_pct, flat_or_apartment_count, flat_or_apartment_pct, flat_one_or_two_storey_block_count, flat_one_or_two_storey_block_pct, flat_three_storey_block_count, flat_three_storey_block_pct, flat_four_to_eight_storey_block_count, flat_four_to_eight_storey_block_pct, flat_nine_plus_storey_block_count, flat_nine_plus_storey_block_pct, flat_attached_to_house_count, flat_attached_to_house_pct, other_dwelling_count, other_dwelling_pct, caravan_count, caravan_pct, cabin_or_houseboat_count, cabin_or_houseboat_pct, improvised_home_or_tent_count, improvised_home_or_tent_pct, attached_to_shop_or_office_count, attached_to_shop_or_office_pct, structure_not_stated_count, structure_not_stated_pct, total_private_dwellings, unoccupied_count, unoccupied_pct. Omit for all.
suburb_nameYesSuburb name exactly as /v1/suburbs/list returns it, e.g. `Bondi` or `St Kilda (Vic.)`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description's added value is coverage limits, a currency date, and a per-call price of 5¢ — useful operational context an agent would not otherwise have. It also links to a full description/method endpoint. It omits result shape and what happens when a suburb has suppressed figures.

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 opening sentence front-loads the resource, and the coverage and price lines are short and scannable. It repeats itself slightly by stating the snapshot date twice ('one snapshot at 10 August 2021' then 'Current to 2021-08-10'), but nothing else is wasted.

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 complex 34-field census dataset with no output schema, the description supplies scope, geography, vintage, cost, and a documentation pointer, which is enough to call it correctly. The gaps are around geographic naming (suburb vs council area) and period filtering within a single-snapshot dataset.

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 description coverage is 100%, so the schema already documents suburb_name, from, to, and the full fields list, making 3 the baseline. The description adds no format or semantics beyond the schema and never reconciles the from/to period filters with its claim of a single 2021 snapshot, nor explains why a suburb_name parameter covers council areas.

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 states a concrete resource: dwelling structure composition — separate houses, semi-detached/townhouses, flats by storey height, other dwellings, plus unoccupied counts. That is far more specific than the title or name. It does not, however, distinguish itself from the sibling lga_area_stats_dwelling_structure, even though it claims to cover council areas too, leaving the boundary between the two unclear.

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?

Usage context is implied through the coverage statement — ~11,500 suburbs and 545 council areas, a single 10 August 2021 snapshot, areas with too few people dropped. There is no explicit when-to-use or when-not, and no pointer to the LGA sibling for council-area queries, so an agent must infer which dwelling-structure tool to pick.

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