Microburbs Australian Property Data

by au.com.microburbs

Overview Discussions Admin

Suburb · Livability narrative sentences

suburbs_lifestyle_narrative

Read-onlyIdempotent

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

One plain-English sentence per livability dimension for the suburb.

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

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 narrative sentences.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "sentences": {
-              "affluence": "37% own outright. Only 10% hold university degrees. Household income $1,728/wk.",
-              "convenience": "No train nearby (9 km). Nearest supermarket: Coles (851m). Hospital 2.9 km."
-            }
-          },
-          "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"
-            },
-            "sentences": {
-              "additionalProperties": true,
-              "description": "Per-dimension sentences.",
-              "properties": {
-                "affluence": {
-                  "anyOf": [
-                    {
-                      "type": "string"
-                    },
-                    {
-                      "type": "null"
-                    }
-                  ],
-                  "description": "Affluence narrative.",
-                  "title": "Affluence"
-                },
-                "community": {
-                  "anyOf": [
-                    {
-                      "type": "string"
-                    },
-                    {
-                      "type": "null"
-                    }
-                  ],
-                  "description": "Community narrative.",
-                  "title": "Community"
-                },
-                "convenience": {
-                  "anyOf": [
-                    {
-                      "type": "string"
-                    },
-                    {
-                      "type": "null"
-                    }
-                  ],
-                  "description": "Convenience narrative.",
-                  "title": "Convenience"
-                },
-                "family": {
-                  "anyOf": [
-                    {
-                      "type": "string"
-                    },
-                    {
-                      "type": "null"
-                    }
-                  ],
-                  "description": "Family narrative.",
-                  "title": "Family"
-                },
-                "hip": {
-                  "anyOf": [
-                    {
-                      "type": "string"
-                    },
-                    {
-                      "type": "null"
-                    }
-                  ],
-                  "description": "Hip narrative.",
-                  "title": "Hip"
-                },
-                "lifestyle": {
-                  "anyOf": [
-                    {
-                      "type": "string"
-                    },
-                    {
-                      "type": "null"
-                    }
-                  ],
-                  "description": "Lifestyle narrative.",
-                  "title": "Lifestyle"
-                },
-                "tranquility": {
-                  "anyOf": [
-                    {
-                      "type": "string"
-                    },
-                    {
-                      "type": "null"
-                    }
-                  ],
-                  "description": "Tranquility narrative.",
-                  "title": "Tranquility"
-                }
-              },
-              "title": "NarrativeSentences",
-              "type": "object"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "sentences"
-          ],
-          "title": "LifestyleNarrative",
-          "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[LifestyleNarrative]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_LifestyleNarrative_"
-}New value: +null

First observedSep 14, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description contributes genuinely new context beyond annotations: the unit cost (10¢ per call) and the output grain (one sentence per dimension), which are useful for cost-aware planning. It stops short of noting query cost caveats such as caching or whether unknown suburbs error out.

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 lines, no filler, with the output description and pricing each clearly separated. The framing sentence about the card location earns its place as disambiguation context, though the bolded pricing line could be folded into a single sentence.

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 does carry the return-shape burden and does say output is one sentence per dimension, which is adequate. However, it omits how many dimensions appear and how suburb names should be formatted, leaving gaps an agent would need to discover by trial.

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 0% and the description adds nothing about the single required parameter suburb_name — no format, matching rules, or ambiguity handling (e.g. suburb plus state). The parameter is guessable from its name, but the description does not fulfill the compensation burden low schema coverage requires.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the resource produced ('one plain-English sentence per livability dimension for the suburb') and where it surfaces ('Livability' card in the Lifestyle section), but it never names a verb or explicitly distinguishes this narrative output from the sibling suburbs_lifestyle_livability data tool. An agent can infer it returns prose rather than scores, but the contrast is left implicit.

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?

Placement guidance ('shown in the suburb report as the Livability card') implies report-rendering usage, but there is no explicit when-to-use versus suburbs_lifestyle_livability or suburbs_lifestyle_summary, and no stated prerequisites. Usage is implied rather than directed.

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?