Microburbs Australian Property Data

Suburb boundary polygon

suburbs_shapes_boundary

Read-onlyIdempotent

Simplified SAL boundary polygon (GeoJSON Feature) plus centroid.

Price: 10¢ 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_shapes_boundary"
  }
}

Input Schema

Name	Required	Description	Default
`geojson`	No	When false, geometry is dropped — every Feature keeps its `properties` but its `geometry` is null. Use it to fetch the counts and per-feature attributes without the coordinates (default true — response unchanged).
`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": "Simplified suburb boundary polygon plus centroid.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "centroid": {
-              "lat": -32.9931,
-              "lng": 151.6688
-            },
-            "geojson": {
-              "geometry": {
-                "coordinates": [
-                  [
-                    [
-                      151.66,
-                      -32.99
-                    ],
-                    [
-                      151.67,
-                      -32.99
-                    ],
-                    [
-                      151.67,
-                      -33
-                    ],
-                    [
-                      151.66,
-                      -32.99
-                    ]
-                  ]
-                ],
-                "type": "Polygon"
-              },
-              "properties": {
-                "suburb": "Belmont North"
-              },
-              "type": "Feature"
-            }
-          },
-          "properties": {
-            "area_level": {
-              "const": "suburb",
-              "description": "Always 'suburb'.",
-              "title": "Area Level",
-              "type": "string"
-            },
-            "area_name": {
-              "description": "Canonical ABS SAL name.",
-              "title": "Area Name",
-              "type": "string"
-            },
-            "centroid": {
-              "description": "Boundary centroid (map-centre hint).",
-              "example": {
-                "lat": -32.9931,
-                "lng": 151.6688
-              },
-              "properties": {
-                "lat": {
-                  "description": "Latitude (WGS84).",
-                  "title": "Lat",
-                  "type": "number"
-                },
-                "lng": {
-                  "description": "Longitude (WGS84).",
-                  "title": "Lng",
-                  "type": "number"
-                }
-              },
-              "required": [
-                "lat",
-                "lng"
-              ],
-              "title": "Centroid",
-              "type": "object"
-            },
-            "geojson": {
-              "additionalProperties": true,
-              "description": "GeoJSON Feature — the SAL boundary polygon, simplified (topology-preserving, ~10 m tolerance, 6 dp coordinates). Geometry is null on every Feature when the request passes `?geojson=false`.",
-              "title": "Geojson",
-              "type": "object"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "centroid",
-            "geojson"
-          ],
-          "title": "SuburbBoundary",
-          "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[SuburbBoundary]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SuburbBoundary_"
-}New value: +null

First observedSep 14, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds two useful facts not in structured fields: the geometry is 'simplified' (generalized, not survey-grade) and each call costs 10¢. It omits coordinate reference system, whether the feature collection has exactly one feature, and how the centroid is represented.

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?

Two compact sentences, return value first, cost second. Nothing is wasted and the price is impossible to miss.

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?

With no output schema, the description carries the burden of explaining returns; naming GeoJSON Feature plus centroid is a reasonable start but leaves field names, centroid property name, and geometry precision unstated. The undocumented suburb_name format is also a gap an agent will hit on first call.

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 coverage is 50%: the geojson flag is well documented in the schema, but suburb_name has no description anywhere. The description does not say whether suburb_name expects a name string, an SAL code, or a case-sensitive match, nor give an example. With half the parameters undocumented, the description should compensate and does not.

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?

States a specific output: a simplified SAL boundary polygon as a GeoJSON Feature plus a centroid. An agent knows exactly what it gets back. It does not distinguish itself from shape siblings (neighbours, hazards, easements) or from geocode_suburb, so it stops short of 5.

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?

No when-to-use guidance at all. Nothing says whether to prefer this over geocode_suburb for getting a suburb's location, or when the boundary geometry is the right input versus a point.

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?