Microburbs Australian Property Data

by au.com.microburbs

Overview Discussions Admin

Land Value (by suburb)

suburbs_market_land_values

Read-onlyIdempotent

Shown in the suburb report as the 'Land Value' card in the Market section.

Suburb land-value medians ($/sqm, lot size, land share of price) + per-mesh-block $/sqm.

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

Input Schema

Name	Required	Description	Default
`suburb_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

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": "Suburb land-value medians + per-mesh-block $/sqm.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "land_share_of_price": 0.546,
-            "mbs": [
-              {
-                "lv_sqm": 748.2,
-                "mb": "10431160000",
-                "n_parcels": 21
-              }
-            ],
-            "median_land_size": 645,
-            "median_land_value": 426078,
-            "median_lv_sqm": 657,
-            "median_price": 780000,
-            "n_parcels": 1549
-          },
-          "properties": {
-            "area_level": {
-              "description": "Always 'suburb' for these endpoints.",
-              "title": "Area Level",
-              "type": "string"
-            },
-            "area_name": {
-              "description": "Suburb (SAL) name.",
-              "title": "Area Name",
-              "type": "string"
-            },
-            "land_share_of_price": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Land value as share of property price (decimal, 0.55 = 55%).",
-              "title": "Land Share Of Price"
-            },
-            "mbs": {
-              "description": "Per-mesh-block land values.",
-              "items": {
-                "description": "Land value $/sqm for one mesh block.",
-                "properties": {
-                  "lv_sqm": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Median land value per square metre (AUD).",
-                    "title": "Lv Sqm"
-                  },
-                  "mb": {
-                    "description": "ABS mesh-block code (MB_CODE21).",
-                    "title": "Mb",
-                    "type": "string"
-                  },
-                  "n_parcels": {
-                    "anyOf": [
-                      {
-                        "type": "integer"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Parcels behind the median.",
-                    "title": "N Parcels"
-                  }
-                },
-                "required": [
-                  "mb"
-                ],
-                "title": "LandValueMb",
-                "type": "object"
-              },
-              "title": "Mbs",
-              "type": "array"
-            },
-            "median_land_size": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Median lot size (sqm).",
-              "title": "Median Land Size"
-            },
-            "median_land_value": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Median total parcel land value (AUD).",
-              "title": "Median Land Value"
-            },
-            "median_lv_sqm": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Median land value per square metre (AUD).",
-              "title": "Median Lv Sqm"
-            },
-            "median_price": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Median property price (AUD) — denominator of the land share.",
-              "title": "Median Price"
-            },
-            "n_parcels": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Parcels behind the suburb medians.",
-              "title": "N Parcels"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "mbs"
-          ],
-          "title": "SuburbLandValues",
-          "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[SuburbLandValues]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SuburbLandValues_"
-}New value: +null

First observedSep 14, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description adds genuine value beyond that by disclosing the cost ('20¢ per call') and enumerating the payload dimensions, which an agent needs before deciding to spend a call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short overall, but the lead sentence is about UI placement rather than the operation, so the definition is not front-loaded with its most useful content. The payload sentence and price line earn their place; the opening sentence is filler from an agent's perspective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 must describe returns and it does so concretely (median $/sqm, lot size, land share of price, per-mesh-block breakdown), and it adds cost. For a single-parameter read tool, this covers everything needed to call it correctly apart from the suburb_name format.

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?

There is one required parameter with 0% schema description coverage, so the description carries the burden and only partially discharges it. 'By suburb' implies suburb_name identifies a suburb, but no format, state qualifier, or naming convention is given for a string that must resolve to a specific place.

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 resource precisely – suburb land-value medians in $/sqm, lot size, land share of price, plus per-mesh-block $/sqm – so an agent knows exactly what data comes back. It lacks an explicit verb (retrieve/return) and does nothing to distinguish it from the sibling 'properties_valuation_land_values', which sounds closely related.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only contextual statement is where the data surfaces in the UI ('Land Value card in the Market section'), which is presentation context, not when-to-use guidance. There is no mention of when to prefer this over properties_valuation_land_values or any other land/valuation sibling, and no prerequisites or exclusions.

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 tools Inspect

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

Need Help?