Microburbs Australian Property Data

Suburb · Livability narrative sentences

suburbs_lifestyle_narrative

Read-onlyIdempotent

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

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": "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.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds that the output is one sentence per livability dimension, which clarifies the response structure. However, it does not disclose potential errors, performance characteristics, or the exact set of dimensions, leaving gaps beyond the annotations.

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?

The description is a single, clear sentence with no filler. It front-loads the core information and is easy to parse. Every word contributes to understanding the tool's purpose.

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?

The tool is simple (one parameter, no output schema), and the description gives a basic idea of the return type. However, it does not enumerate the livability dimensions or clarify the exact data structure (e.g., object vs list), which could be helpful given the absence of an output schema. It is minimally sufficient but not comprehensive.

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 description coverage is 0%, and the description does not compensate. The single parameter, suburb_name, is self-explanatory by name, but the description adds no format, validation, or example. For a low-coverage schema, the description should provide at least a hint about acceptable values or usage, which it 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?

The description states a clear action: provide one plain-English sentence per livability dimension for a suburb. It specifies the resource (suburb) and the output format, distinguishing it from data-heavy or map-based siblings like suburbs_lifestyle_livability. However, it does not explicitly name alternative tools or conditions for choosing this one.

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 description gives no guidance on when to use this tool versus its siblings. It does not mention scenarios, prerequisites, or exclusions. An agent must infer from the name and title that it returns narrative text rather than raw data, but there is no explicit direction.

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?