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).

Price: 5¢ 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_landmarks"
  }
}

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": "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

A3.6/5.0

Behavior4/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 the bar is lower. The description still adds real context beyond them: distances are straight-line rather than travel distance, a null means nothing within ~50 km, and each call costs 5¢ — all decision-relevant for an agent budgeting calls.

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?

Two short sentences, front-loaded with what is returned, followed by the cost line. Nothing is redundant, though the pricing statement reads as a bolt-on rather than integrated context.

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 the return-value burden; it explains the distance semantics and null case but not the response shape (whether facility names, addresses, or coordinates are included). Adequate for a simple lookup but with a clear gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter (suburb_name) with 0% schema description coverage, and the description says nothing about its expected format or matching behavior. Because only one simple parameter exists, minimal compensation is needed, but the gap is unaddressed.

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 specific resource pair (nearest beach and hospital) and what is returned (straight-line distances), so an agent can tell what the tool produces. It does not distinguish itself from nearby siblings such as suburbs_lifestyle_pois or suburbs_amenities_health_services, which likely overlap.

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?

Usage is only implied by the stated purpose: an agent can infer it should be called when nearest-beach or nearest-hospital proximity is needed. There is no explicit when-to-use/when-not guidance and no pointer to alternative lifestyle or amenities tools for broader POI needs.

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?