Microburbs Australian Property Data

Suburb · Distance to the nearest city and to the nearest capital

suburbs_lifestyle_cbd

Read-onlyIdempotent

Straight-line distance to the nearest city and to the nearest capital, in km.

Both, because they answer different questions and are often nowhere near each other: Belmont North is 14 km from Newcastle and 108 km from Sydney. nearest_city is usually what a buyer means by "how far is town".

The top-level city / distance_km fields are DEPRECATED. They still describe the CAPITAL, unchanged, so existing callers are unaffected — read capital_city or nearest_city instead.

Input Schema

TableJSON 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": "Distance to the nearest city and to the nearest capital.\n\nThese are different places and often very different distances — Belmont\nNorth is 14 km from Newcastle and 108 km from Sydney. Read whichever\nanswers your question; `nearest_city` is usually the one a buyer means.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "capital_city": {
-              "distance_km": 108,
-              "name": "Sydney"
-            },
-            "city": "Sydney",
-            "distance_km": 108,
-            "nearest_city": {
-              "distance_km": 14,
-              "name": "Newcastle"
-            }
-          },
-          "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"
-            },
-            "capital_city": {
-              "anyOf": [
-                {
-                  "additionalProperties": true,
-                  "description": "A named city and the straight-line distance to it.",
-                  "properties": {
-                    "distance_km": {
-                      "description": "Straight-line distance (km).",
-                      "title": "Distance Km",
-                      "type": "number"
-                    },
-                    "name": {
-                      "anyOf": [
-                        {
-                          "type": "string"
-                        },
-                        {
-                          "type": "null"
-                        }
-                      ],
-                      "description": "City name (e.g. 'Newcastle').",
-                      "title": "Name"
-                    }
-                  },
-                  "required": [
-                    "distance_km"
-                  ],
-                  "title": "CityDistance",
-                  "type": "object"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Nearest state/territory capital, and the distance to it."
-            },
-            "city": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "DEPRECATED — the CAPITAL's name. Use `capital_city.name`.",
-              "title": "City"
-            },
-            "distance_km": {
-              "description": "DEPRECATED — distance to the CAPITAL, not to the nearest city. Use `capital_city.distance_km`, or `nearest_city.distance_km`.",
-              "title": "Distance Km",
-              "type": "number"
-            },
-            "nearest_city": {
-              "anyOf": [
-                {
-                  "additionalProperties": true,
-                  "description": "A named city and the straight-line distance to it.",
-                  "properties": {
-                    "distance_km": {
-                      "description": "Straight-line distance (km).",
-                      "title": "Distance Km",
-                      "type": "number"
-                    },
-                    "name": {
-                      "anyOf": [
-                        {
-                          "type": "string"
-                        },
-                        {
-                          "type": "null"
-                        }
-                      ],
-                      "description": "City name (e.g. 'Newcastle').",
-                      "title": "Name"
-                    }
-                  },
-                  "required": [
-                    "distance_km"
-                  ],
-                  "title": "CityDistance",
-                  "type": "object"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Nearest city of any size, and the distance to it."
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "distance_km"
-          ],
-          "title": "LifestyleCbd",
-          "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[LifestyleCbd]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_LifestyleCbd_"
-}New value: +null

First observedSep 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the bar is lower. The description adds behavioral context beyond that: the distances are straight-line, expressed in km, and the top-level city/distance_km fields are deprecated but still describe the capital unchanged. This is valuable field-level transparency and does not contradict any annotation.

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 core purpose is front-loaded in the first sentence, and the following paragraphs add useful nuance and deprecation guidance. No sentence is purely filler, though the middle paragraph could be slightly tightened without losing meaning.

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 a good job of naming the important output fields (nearest_city, capital_city, city, distance_km), their units, and their deprecation status. For a simple one-parameter read-only lookup, this is nearly complete; missing details such as the full response object shape are minor.

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?

The only parameter, suburb_name, is never explicitly described. The description implies its meaning through the 'Belmont North' example, but does not state what value the parameter expects, what format is accepted, or whether it is restricted to certain localities. With 0% schema description coverage, this is a clear gap.

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 first sentence precisely identifies the resource and scope: straight-line distance to the nearest city and nearest capital in km. It also distinguishes the two conceptually different measurements and names the relevant fields, so an agent can tell this apart from lifestyle, POI, or transport tools.

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

Usage Guidelines4/5

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

The description explains that nearest_city and capital_city answer different questions and gives a practical heuristic (nearest_city is usually what a buyer means). It also deprecates the old city/distance_km fields and directs callers to the correct replacement fields. It does not explicitly name a sibling tool as an alternative, so it stops short of a 5.

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?