Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

New supply, units vs houses, by mesh block (by suburb)

suburbs_development_supply
Read-onlyIdempotent

Shown in the suburb report as the 'Supply 2km' map layer (explorer) in the Development section.

New dwellings (last 24 months) split units vs houses. summary counts each new building once inside the suburb; each mesh block row counts new dwellings within 500 m of the block centre, so block rows overlap and must not be summed.

Price: 20¢ 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_development_supply"
  }
}

Input Schema

NameRequiredDescriptionDefault
suburb_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "available": {
-      "anyOf": [
-        {
-          "type": "boolean"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "`false` on no-data responses. Omitted on success — branch on `data !== null` if you want a single discriminator.",
-      "title": "Available"
-    },
-    "data": {
-      "anyOf": [
-        {
-          "additionalProperties": true,
-          "description": "New dwelling supply — units vs houses per mesh block + rollup.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "mesh_blocks": [
-              {
-                "mb_code": "10694560000",
-                "new_houses": 15,
-                "new_units": 3,
-                "pct_units": 16.7,
-                "total_new": 18
-              }
-            ],
-            "summary": {
-              "new_houses": 650,
-              "new_units": 410,
-              "pct_houses": 61.3,
-              "pct_units": 38.7,
-              "total_new": 1060
-            }
-          },
-          "properties": {
-            "area_level": {
-              "description": "Always 'suburb'.",
-              "title": "Area Level",
-              "type": "string"
-            },
-            "area_name": {
-              "description": "Suburb (SAL) name.",
-              "title": "Area Name",
-              "type": "string"
-            },
-            "mesh_blocks": {
-              "description": "Per-mesh-block rows, most new supply first.",
-              "items": {
-                "additionalProperties": true,
-                "description": "New supply near one mesh block (0.5 km radius, last 24 months).",
-                "properties": {
-                  "mb_code": {
-                    "description": "ABS mesh-block code.",
-                    "title": "Mb Code",
-                    "type": "string"
-                  },
-                  "new_houses": {
-                    "description": "New houses appearing in GNAF.",
-                    "title": "New Houses",
-                    "type": "integer"
-                  },
-                  "new_units": {
-                    "description": "New units appearing in GNAF.",
-                    "title": "New Units",
-                    "type": "integer"
-                  },
-                  "pct_units": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Unit share of new supply (%); null when no new supply.",
-                    "title": "Pct Units"
-                  },
-                  "total_new": {
-                    "description": "Total new dwellings (houses + units).",
-                    "title": "Total New",
-                    "type": "integer"
-                  }
-                },
-                "required": [
-                  "mb_code",
-                  "new_houses",
-                  "new_units",
-                  "total_new"
-                ],
-                "title": "SupplyMb",
-                "type": "object"
-              },
-              "title": "Mesh Blocks",
-              "type": "array"
-            },
-            "summary": {
-              "description": "Suburb rollup.",
-              "properties": {
-                "new_houses": {
-                  "description": "Total new houses across mesh blocks.",
-                  "title": "New Houses",
-                  "type": "integer"
-                },
-                "new_units": {
-                  "description": "Total new units across mesh blocks.",
-                  "title": "New Units",
-                  "type": "integer"
-                },
-                "pct_houses": {
-                  "anyOf": [
-                    {
-                      "type": "number"
-                    },
-                    {
-                      "type": "null"
-                    }
-                  ],
-                  "description": "House share of new supply (%); null when zero supply.",
-                  "title": "Pct Houses"
-                },
-                "pct_units": {
-                  "anyOf": [
-                    {
-                      "type": "number"
-                    },
-                    {
-                      "type": "null"
-                    }
-                  ],
-                  "description": "Unit share of new supply (%); null when zero supply.",
-                  "title": "Pct Units"
-                },
-                "total_new": {
-                  "description": "Total new dwellings.",
-                  "title": "Total New",
-                  "type": "integer"
-                }
-              },
-              "required": [
-                "new_houses",
-                "new_units",
-                "total_new"
-              ],
-              "title": "SupplySummary",
-              "type": "object"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "summary",
-            "mesh_blocks"
-          ],
-          "title": "SuburbDevelopmentSupply",
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "The endpoint's payload, or `null` when Microburbs has no value."
-    },
-    "message": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "Human-readable explanation. Omitted on success.",
-      "title": "Message"
-    },
-    "reason": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "Machine-readable slug naming the no-data condition (e.g. `no_avm_for_GANSW704074813`). Stable per endpoint. Omitted on success.",
-      "title": "Reason"
-    }
-  },
-  "title": "ApiResponse[SuburbDevelopmentSupply]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SuburbDevelopmentSupply_"
-}New value: +null
  2. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed world), and the description goes well beyond them: it discloses a per-call price of 20¢, the 24-month time window, and the critical fact that mesh-block rows are 500 m-radius counts that overlap. That overlap warning is exactly the kind of behavior an agent could not infer from structured fields and would otherwise get wrong.

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?

Roughly five short sentences with no filler, and the cost line is isolated so it is hard to miss. The first sentence is a locator rather than the purpose, which slightly delays the key information, but nothing is redundant.

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 does the necessary work of explaining the two row granularities and the summation hazard, plus cost. It stops short of describing the actual returned fields (counts, geography identifiers) and the suburb_name input contract.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter is only named, never explained. Nothing states the expected `suburb_name` format, whether it must match a canonical suburb, or whether geocoding is a prerequisite, so the agent must guess at input validity.

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 names a concrete resource and scope: new dwellings over the last 24 months split into units vs houses, delivered both as a suburb-level `summary` and per-mesh-block rows. Combined with the report-layer locator ('Supply 2km' in the Development section), an agent can tell this apart from generic development or market-supply siblings without opening a schema.

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 via its place in the suburb report; there is no explicit statement of when to call this instead of, for example, the new-dwellings map or supply-pressure siblings. The one piece of real guidance is interpretive rather than selective: block rows overlap and must not be summed, which steers the agent toward `summary` for totals.

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