Microburbs Australian Property Data

Suburb · Nearest beach + hospital

suburbs_lifestyle_landmarks

Read-onlyIdempotent

Nearest beach and hospital with straight-line distances (null = none within ~50 km).

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": "Nearest beach and hospital (null = none within ~50 km).",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "nearest_beach": {
-              "dist_km": 1.5,
-              "name": "Redhead Beach, NSW"
-            },
-            "nearest_hospital": {
-              "dist_km": 1.4,
-              "name": "Narla Village"
-            }
-          },
-          "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"
-            },
-            "nearest_beach": {
-              "anyOf": [
-                {
-                  "additionalProperties": true,
-                  "description": "A named landmark with straight-line distance.",
-                  "properties": {
-                    "dist_km": {
-                      "description": "Straight-line distance (km).",
-                      "title": "Dist Km",
-                      "type": "number"
-                    },
-                    "name": {
-                      "anyOf": [
-                        {
-                          "type": "string"
-                        },
-                        {
-                          "type": "null"
-                        }
-                      ],
-                      "description": "Landmark name.",
-                      "title": "Name"
-                    }
-                  },
-                  "required": [
-                    "dist_km"
-                  ],
-                  "title": "LandmarkPlace",
-                  "type": "object"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Nearest beach."
-            },
-            "nearest_hospital": {
-              "anyOf": [
-                {
-                  "additionalProperties": true,
-                  "description": "A named landmark with straight-line distance.",
-                  "properties": {
-                    "dist_km": {
-                      "description": "Straight-line distance (km).",
-                      "title": "Dist Km",
-                      "type": "number"
-                    },
-                    "name": {
-                      "anyOf": [
-                        {
-                          "type": "string"
-                        },
-                        {
-                          "type": "null"
-                        }
-                      ],
-                      "description": "Landmark name.",
-                      "title": "Name"
-                    }
-                  },
-                  "required": [
-                    "dist_km"
-                  ],
-                  "title": "LandmarkPlace",
-                  "type": "object"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Nearest hospital."
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level"
-          ],
-          "title": "LifestyleLandmarks",
-          "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[LifestyleLandmarks]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_LifestyleLandmarks_"
-}New value: +null

First observedSep 14, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description is not required to repeat those. It adds meaningful behavioral context by specifying the straight-line distance metric and the null = none within ~50 km rule. It does not disclose response shape or data source, but it adds value 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 efficient sentence that front-loads the main output and appends the null-semantics rule in a parenthetical. No filler or redundant restatement of the schema or annotations.

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?

For a one-parameter lookup tool, the description conveys the output and the distance threshold, and annotations cover safety. However, with no output schema and no guidance on acceptable suburb_name formats or whether the name must match a canonical list, an agent cannot fully anticipate the response structure or valid inputs.

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 input schema has 0% description coverage for suburb_name, and the tool description does not mention the parameter at all. The name is self-explanatory, but because the schema provides no documentation and the description does not compensate, there is no added semantic value.

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 clearly states the tool returns the nearest beach and hospital with straight-line distances, which is specific and distinguishes it from the many suburbs_lifestyle_* siblings. It lacks an explicit verb like 'gets' or 'returns,' but the output contract is unambiguous.

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 usage guidance is provided. The description does not mention when to prefer this tool over alternatives such as suburbs_lifestyle_pois, suburbs_lifestyle_cbd, or suburbs_lifestyle_summary, so the agent must infer applicability from the name and title alone.

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?