Skip to main content
Glama

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

POIs / amenities in the suburb (pubs, cafes, gyms, schools, …)

suburbs_lifestyle_pois
Read-onlyIdempotent

Every named venue / amenity in the suburb as GeoJSON Point features, plus a per-category count.

Each point carries name, a broad category (Restaurant / Cafe, Shopping, Health, Entertainment, Sport & Fitness, Education, …) and a finer subtype (e.g. pub, bar, cafe, restaurant, gym, supermarket, school, pharmacy). This is the endpoint for "what / how many are in this suburb" and "name the pubs / cafes / gyms in X" — filter or count the features on subtype, and read real venue names from name. The top-level categories array gives the broad-category counts without walking the list.

Unpaged by default. Big suburbs are big — Sydney is ~3.7 MB of features — so pass limit/offset (or narrow with category) when you don't need them all. count and categories always describe the whole suburb, so paging never hides the totals. Flat price per call regardless of page size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoFeatures to return (default: all).
offsetNoFeature offset — page with `limit`.
categoryNoOnly this display category (e.g. `Shopping`). Case-insensitive.
suburb_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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": "Every amenity point in the suburb as GeoJSON, with category counts.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "categories": [
-              {
-                "category": "Shopping",
-                "count": 32
-              },
-              {
-                "category": "Sport & Fitness",
-                "count": 26
-              }
-            ],
-            "count": 177,
-            "pois": {
-              "features": [
-                {
-                  "geometry": {
-                    "coordinates": [
-                      151.66231,
-                      -33.02463
-                    ],
-                    "type": "Point"
-                  },
-                  "properties": {
-                    "category": "Shopping",
-                    "dim": "convenience",
-                    "name": "Ampol Foodary",
-                    "subtype": "newsagent"
-                  },
-                  "type": "Feature"
-                }
-              ],
-              "type": "FeatureCollection"
-            }
-          },
-          "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"
-            },
-            "categories": {
-              "description": "Per-category counts across the whole suburb, largest first.",
-              "items": {
-                "description": "Per-display-category POI count.",
-                "properties": {
-                  "category": {
-                    "description": "Display category.",
-                    "title": "Category",
-                    "type": "string"
-                  },
-                  "count": {
-                    "description": "POIs in the category.",
-                    "title": "Count",
-                    "type": "integer"
-                  }
-                },
-                "required": [
-                  "category",
-                  "count"
-                ],
-                "title": "PoiCategoryCount",
-                "type": "object"
-              },
-              "title": "Categories",
-              "type": "array"
-            },
-            "count": {
-              "description": "POIs available in the suburb (after any `category` filter), counted before `limit`/`offset`.",
-              "title": "Count",
-              "type": "integer"
-            },
-            "pois": {
-              "description": "GeoJSON FeatureCollection of points.",
-              "properties": {
-                "features": {
-                  "description": "One feature per POI.",
-                  "items": {
-                    "description": "One POI as a GeoJSON Feature.",
-                    "properties": {
-                      "geometry": {
-                        "description": "Point location.",
-                        "properties": {
-                          "coordinates": {
-                            "description": "`[longitude, latitude]` — 2 numbers, lon first per GeoJSON.",
-                            "items": {
-                              "type": "number"
-                            },
-                            "title": "Coordinates",
-                            "type": "array"
-                          },
-                          "type": {
-                            "const": "Point",
-                            "description": "Always 'Point'.",
-                            "title": "Type",
-                            "type": "string"
-                          }
-                        },
-                        "required": [
-                          "type",
-                          "coordinates"
-                        ],
-                        "title": "GeoJsonPointGeometry",
-                        "type": "object"
-                      },
-                      "properties": {
-                        "additionalProperties": true,
-                        "description": "Name/category/dim props.",
-                        "properties": {
-                          "category": {
-                            "anyOf": [
-                              {
-                                "type": "string"
-                              },
-                              {
-                                "type": "null"
-                              }
-                            ],
-                            "description": "Display category (e.g. 'Restaurant / Cafe').",
-                            "title": "Category"
-                          },
-                          "dim": {
-                            "anyOf": [
-                              {
-                                "type": "string"
-                              },
-                              {
-                                "type": "null"
-                              }
-                            ],
-                            "description": "Livability dimension the POI contributes to (e.g. 'convenience').",
-                            "title": "Dim"
-                          },
-                          "name": {
-                            "anyOf": [
-                              {
-                                "type": "string"
-                              },
-                              {
-                                "type": "null"
-                              }
-                            ],
-                            "description": "POI name; null for unnamed points.",
-                            "title": "Name"
-                          },
-                          "subtype": {
-                            "anyOf": [
-                              {
-                                "type": "string"
-                              },
-                              {
-                                "type": "null"
-                              }
-                            ],
-                            "description": "L2 subtype — the specific venue type. Filter/count on this for a question like 'how many pubs': e.g. 'pub', 'bar', 'cafe', 'restaurant', 'gym', 'supermarket', 'school', 'pharmacy'.",
-                            "title": "Subtype"
-                          }
-                        },
-                        "title": "PoiFeatureProperties",
-                        "type": "object"
-                      },
-                      "type": {
-                        "const": "Feature",
-                        "description": "Always 'Feature'.",
-                        "title": "Type",
-                        "type": "string"
-                      }
-                    },
-                    "required": [
-                      "type",
-                      "geometry",
-                      "properties"
-                    ],
-                    "title": "PoiFeature",
-                    "type": "object"
-                  },
-                  "title": "Features",
-                  "type": "array"
-                },
-                "type": {
-                  "const": "FeatureCollection",
-                  "description": "Always 'FeatureCollection'.",
-                  "title": "Type",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "type",
-                "features"
-              ],
-              "title": "PoiFeatureCollection",
-              "type": "object"
-            },
-            "returned": {
-              "description": "Features actually in this response — equals `count` when unpaged.",
-              "title": "Returned",
-              "type": "integer"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "count",
-            "returned",
-            "categories",
-            "pois"
-          ],
-          "title": "LifestylePois",
-          "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[LifestylePois]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_LifestylePois_"
-}New value: +null
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already convey read-only, idempotent, non-destructive behavior. The description adds valuable non-obvious behavioral context: unpaged by default, large payloads ('Sydney is ~3.7 MB of features'), paging semantics, and the guarantee that 'count and categories always describe the whole suburb, so paging never hides the totals.' It also discloses flat pricing per call. None of this contradicts 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 moderately long but every sentence earns its place: purpose, data shape, use cases, size warning, paging semantics, totals guarantee, and pricing. The most important information is front-loaded in the first two sentences, and the rest is organized into clear functional sections without repetition or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema present, the description carries the full burden of explaining return values, and it does so thoroughly: GeoJSON Point features, fields `name`, `category`, `subtype`, the `categories` array, and top-level behavior around counts. It also covers the main invocation concerns (pagination, size, filtering) for a tool with two optional parameters and one required parameter. Nothing an agent needs to call and use this tool correctly is missing.

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

Parameters4/5

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

Schema coverage is 75%, so schema descriptions cover limit, offset, and category. The description goes further by explaining how returned `subtype` values (pub, bar, cafe, gym, etc.) should be used for filtering/counting, and that the top-level `categories` array provides counts without walking the list. It also advises narrowing with `category`. This adds meaningful guidance beyond the bare schema, though `suburb_name` is left undocumented.

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

Purpose5/5

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

The description opens with a precise statement of what the tool returns: 'Every named venue / amenity in the suburb as GeoJSON Point features, plus a per-category count.' It gives concrete examples of venue types and explicitly defines the query patterns this endpoint serves ('what / how many <venue type> are in this suburb'). This clearly differentiates it from nearby sibling tools like properties_amenities_nearby or suburbs_lifestyle_landmarks by emphasizing named venues, subtype filtering, and counts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance: it is 'the endpoint for' counting venues and naming pubs/cafes/gyms in a suburb, with direction to 'filter or count the features on `subtype`'. It also advises when to pass limit/offset or narrow with category for large suburbs. However, it does not explicitly mention when not to use it or name alternative sibling tools, so it stops just short of a 5.

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 toolsInspect
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