Suburb · New supply — units vs houses
suburbs_development_supplyRead-onlyIdempotent
New dwellings (last 24 months) split units vs houses per mesh block plus a rollup.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| suburb_name | Yes |
Microburbs Australian Property Data
Schema Changelog
Changes observed during successful MCP inspections.
Changed1 schema field changed
- changed
Output 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
- First observed
TDQS
B3.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the time window (last 24 months) and the aggregation level (mesh block plus rollup), which is useful behavioral context. It doesn't mention pagination, response size, or data availability limitations, but the annotations carry the main safety burden.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that packs the essential information: time window, split dimension, and aggregation level. No wasted words, and the key scoping details are front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with one parameter and no output schema, the description covers the core purpose. However, the lack of parameter format guidance and the absence of any mention of what the response contains (beyond the split) leaves some gaps. The sibling list is large, but the description's specificity helps narrow down the tool's role.
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 only parameter is suburb_name with no description in the schema. The tool description doesn't explain what format suburb_name should take (e.g., 'Sydney' vs 'Sydney NSW'), case sensitivity, or whether it accepts suburb IDs. With zero schema coverage and no parameter guidance in the description, the agent has to guess the expected input format.
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 specific verb and resource: 'New dwellings (last 24 months) split units vs houses per mesh block plus a rollup.' This clearly identifies what the tool does and distinguishes it from generic development tools. However, it doesn't explicitly name a sibling alternative, so it doesn't fully differentiate from similar suburbs_development_* tools.
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 implies usage context: it's for new dwelling supply data over the last 24 months, split by dwelling type and mesh block. It doesn't explicitly state when to use this vs alternatives like suburbs_development_all or suburbs_development_construction_activity, but the specific scope provides some guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.