Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

LGA · Bedrooms

lga_area_stats_bedrooms
Read-onlyIdempotent

How many bedrooms homes have: studios through six or more, for all dwellings and separately for houses, townhouses and apartments, plus people per bedroom, for every suburb and council area.

Coverage: About 10,700 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/bedrooms.

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_bedrooms"
  }
}

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, studio_count, studio_pct, one_bedroom_count, one_bedroom_pct, two_bedrooms_count, two_bedrooms_pct, three_bedrooms_count, three_bedrooms_pct, four_bedrooms_count, four_bedrooms_pct, five_bedrooms_count, five_bedrooms_pct, six_plus_bedrooms_count, six_plus_bedrooms_pct, bedrooms_not_stated_count, bedrooms_not_stated_pct, total_house, house_studio_count, house_studio_pct, house_one_bedroom_count, house_one_bedroom_pct, house_two_bedrooms_count, house_two_bedrooms_pct, house_three_bedrooms_count, house_three_bedrooms_pct, house_four_bedrooms_count, house_four_bedrooms_pct, house_five_bedrooms_count, house_five_bedrooms_pct, house_six_plus_bedrooms_count, house_six_plus_bedrooms_pct, house_bedrooms_not_stated_count, house_bedrooms_not_stated_pct, total_townhouse, townhouse_studio_count, townhouse_studio_pct, townhouse_one_bedroom_count, townhouse_one_bedroom_pct, townhouse_two_bedrooms_count, townhouse_two_bedrooms_pct, townhouse_three_bedrooms_count, townhouse_three_bedrooms_pct, townhouse_four_bedrooms_count, townhouse_four_bedrooms_pct, townhouse_five_bedrooms_count, townhouse_five_bedrooms_pct, townhouse_six_plus_bedrooms_count, townhouse_six_plus_bedrooms_pct, townhouse_bedrooms_not_stated_count, townhouse_bedrooms_not_stated_pct, total_apartment, apartment_studio_count, apartment_studio_pct, apartment_one_bedroom_count, apartment_one_bedroom_pct, apartment_two_bedrooms_count, apartment_two_bedrooms_pct, apartment_three_bedrooms_count, apartment_three_bedrooms_pct, apartment_four_bedrooms_count, apartment_four_bedrooms_pct, apartment_five_bedrooms_count, apartment_five_bedrooms_pct, apartment_six_plus_bedrooms_count, apartment_six_plus_bedrooms_pct, apartment_bedrooms_not_stated_count, apartment_bedrooms_not_stated_pct, persons_per_bedroom. 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 a safe read-only, idempotent, non-destructive, closed-world operation, so the bar is lower and the description clears it by adding coverage scale (about 10,700 suburbs and 545 council areas), the exclusion rule for areas with too few people or homes, the single snapshot date, and a per-call price of 5¢. Those are exactly the traits an agent cannot get from the annotations. It stops short of describing response shape or result-size limits.

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 measure definition is front-loaded in the first sentence, followed by coverage, currency and cost in short blocks, with no filler. The opening sentence is long and carries a lot of enumerations, but each clause conveys distinct scope information.

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?

With no output schema, the description compensates by describing the measures returned and pointing to /v1/datasets/bedrooms for the full field list and method. Coverage, snapshot date and price are all present; the remaining gap is that return structure and the practical effect of from/to on a single-snapshot dataset are unstated.

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 from, to, fields and lga_name in detail, making 3 the baseline. The description does add interpretive value by explaining that the ~70 field names group into all-dwellings / house / townhouse / apartment blocks plus persons per bedroom, but it does not clarify why from/to exist when the data is a single 2021 snapshot.

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 names the specific measure set (bedroom counts from studio through six-plus, split across all dwellings, houses, townhouses and apartments, plus persons per bedroom) and the geography, so an agent can distinguish it from topic siblings like ancestry or dwelling_structure. It is slightly muddied by saying 'for every suburb and council area' when this is the LGA-scoped tool and a separate suburbs_area_stats_bedrooms sibling exists.

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 is only implied by the dataset scope; there is no explicit 'use this when' statement and no reference to the suburbs_area_stats_bedrooms sibling for suburb-level queries. The one concrete routing hint is that lga_name must come from /v1/lga/list, which is useful but is about input validation rather than tool selection.

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