Microburbs Australian Property Data

by au.com.microburbs

Overview Discussions Admin

Suburb · Livability

suburbs_lifestyle_livability

Read-onlyIdempotent

Shown in the suburb report as the 'Livability' card in the Lifestyle section.

Livability scores (0–100) per dimension, aggregated from mesh-block scores, with the SA4 benchmark.

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

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 livability scores (mesh-block average) + regional benchmark.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "benchmark": {
-              "n_suburbs": 149,
-              "region": "Newcastle and Lake Macquarie",
-              "scores": {
-                "affluence": 66.9,
-                "hip": 59.5,
-                "lifestyle": 73.4,
-                "safety": 84.8
-              }
-            },
-            "n_mesh_blocks": 63,
-            "scores": [
-              {
-                "key": "affluence",
-                "label": "Affluence",
-                "level": "Moderate",
-                "value": 56
-              },
-              {
-                "key": "lifestyle",
-                "label": "Lifestyle",
-                "level": "Moderate",
-                "value": 72
-              },
-              {
-                "key": "safety",
-                "label": "Safety",
-                "level": "High",
-                "value": 76
-              }
-            ]
-          },
-          "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"
-            },
-            "benchmark": {
-              "anyOf": [
-                {
-                  "additionalProperties": true,
-                  "description": "SA4-region benchmark for comparing the suburb's scores.",
-                  "properties": {
-                    "n_suburbs": {
-                      "description": "Suburbs in the region.",
-                      "title": "N Suburbs",
-                      "type": "integer"
-                    },
-                    "region": {
-                      "description": "SA4 region name.",
-                      "title": "Region",
-                      "type": "string"
-                    },
-                    "scores": {
-                      "description": "Region-average scores.",
-                      "properties": {
-                        "affluence": {
-                          "anyOf": [
-                            {
-                              "type": "number"
-                            },
-                            {
-                              "type": "null"
-                            }
-                          ],
-                          "description": "Region average affluence.",
-                          "title": "Affluence"
-                        },
-                        "hip": {
-                          "anyOf": [
-                            {
-                              "type": "number"
-                            },
-                            {
-                              "type": "null"
-                            }
-                          ],
-                          "description": "Region average hip.",
-                          "title": "Hip"
-                        },
-                        "lifestyle": {
-                          "anyOf": [
-                            {
-                              "type": "number"
-                            },
-                            {
-                              "type": "null"
-                            }
-                          ],
-                          "description": "Region average lifestyle.",
-                          "title": "Lifestyle"
-                        },
-                        "safety": {
-                          "anyOf": [
-                            {
-                              "type": "number"
-                            },
-                            {
-                              "type": "null"
-                            }
-                          ],
-                          "description": "Region average safety.",
-                          "title": "Safety"
-                        }
-                      },
-                      "title": "LivabilityBenchmarkScores",
-                      "type": "object"
-                    }
-                  },
-                  "required": [
-                    "region",
-                    "n_suburbs",
-                    "scores"
-                  ],
-                  "title": "LivabilityBenchmark",
-                  "type": "object"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "SA4 benchmark; null when the region has no bench row."
-            },
-            "n_mesh_blocks": {
-              "description": "Mesh blocks the scores aggregate over.",
-              "title": "N Mesh Blocks",
-              "type": "integer"
-            },
-            "scores": {
-              "description": "One entry per dimension.",
-              "items": {
-                "additionalProperties": true,
-                "description": "One livability dimension score (0–100).",
-                "properties": {
-                  "key": {
-                    "description": "Dimension key — affluence | lifestyle | hip | convenience | family | safety | tranquility.",
-                    "title": "Key",
-                    "type": "string"
-                  },
-                  "label": {
-                    "description": "Human dimension label.",
-                    "title": "Label",
-                    "type": "string"
-                  },
-                  "level": {
-                    "description": "Human level — Very low / Low / Moderate / High / Very high.",
-                    "title": "Level",
-                    "type": "string"
-                  },
-                  "value": {
-                    "anyOf": [
-                      {
-                        "type": "integer"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Score 0–100; null when no data.",
-                    "title": "Value"
-                  }
-                },
-                "required": [
-                  "key",
-                  "label",
-                  "level"
-                ],
-                "title": "LivabilityScore",
-                "type": "object"
-              },
-              "title": "Scores",
-              "type": "array"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "n_mesh_blocks",
-            "scores"
-          ],
-          "title": "LifestyleLivability",
-          "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[LifestyleLivability]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_LifestyleLivability_"
-}New value: +null

First observedSep 14, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the bar is lower. The description still adds real value beyond them: a per-call price of 10¢ (important for cost-aware agents), the aggregation method (mesh-block to dimension), and the comparison baseline (SA4 benchmark). It does not disclose which dimensions are returned or how missing suburbs are handled.

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?

Three short, dense clauses with no padding; the data definition is front-loaded after a brief locational frame. The report-card sentence is arguably dispensable but does provide orientation. Nothing is redundant.

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 must carry return-value semantics, which it partially does (score range, aggregation, benchmark). However, it omits the dimension list, the shape of the benchmark comparison, and any parameter guidance, which leaves meaningful gaps for a data-retrieval tool with competing siblings.

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?

There is a single required parameter, suburb_name, at 0% schema description coverage, and the description never mentions it. It gives no indication of expected format (exact name vs. fuzzy match), whether a preceding geocode_suburb lookup is needed, or how ambiguous names resolve. With zero schema coverage, the description was the only place this could be specified.

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 identifies a specific resource and its output shape: livability scores (0-100) per dimension, mesh-block aggregated, plus an SA4 benchmark. It also anchors the data to a named card ('Livability' in the Lifestyle section). It stops short of differentiating itself from close siblings such as suburbs_lifestyle_livability_map or suburbs_lifestyle_summary.

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 usage signal is where the data appears in a report card, which is display context rather than guidance on when to call this tool. There is no statement of when to prefer it over suburbs_lifestyle_livability_map, suburbs_lifestyle_summary, or suburbs_lifestyle_narrative, and no exclusions or prerequisites.

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?