Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

LGA · Dwelling structure

lga_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": {
      "lga_name": "<lga_name>"
    },
    "name": "lga_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.
lga_nameYesCouncil (LGA) name exactly as /v1/lga/list returns it, e.g. `Lake Macquarie`.

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 declare readOnly/idempotent/non-destructive, so safety is covered; the description adds genuinely useful behavior beyond that: a 5¢ per-call price, the static 10 Aug 2021 currency, and the rule that areas with too few people or homes are omitted. It does not describe result shape or pagination, but there is no output schema and it defers to a documented field list.

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?

Front-loaded with the substance (what dwelling categories and vacancy data are returned), followed by coverage, currency and price. Every sentence carries information; the only redundancy is the overlap between 'current to 2021-08-10' and 'one snapshot at 10 August 2021'.

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 data-retrieval tool with no output schema, the description supplies what an agent needs to call it responsibly: coverage boundaries, temporal currency, cost, and a pointer to the field list and method. It would be complete at 5 if it clarified the LGA-vs-suburb scope implied by the sibling names.

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 100% (each of from/to/fields/lga_name is documented inline, including the format examples for periods and the full field enumeration), so the schema carries parameter meaning. The description adds nothing about parameter usage — it does not restate the 'name exactly as /v1/lga/list returns it' requirement or the field-subset behavior — so baseline 3 applies.

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?

States a specific resource (dwelling structure by dwelling type, plus unoccupied dwellings) and verb-level scope of what it returns. The phrase 'for every suburb and council area' is the only fuzzy spot — the tool is LGA-level, so it slightly blurs against suburbs_area_stats_dwelling_structure, but an agent can still tell it retrieves dwelling-structure stats.

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?

The description gives coverage context (which areas are included/excluded, the 2021 snapshot) and links a dataset doc page for full method, which implies when the data is appropriate. It never states when to prefer it over the suburb-level sibling or over the raw datasets/area_stats_values tools, and offers no exclusions, so usage is only implied.

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