Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb at a glance

suburbs_hero_summary
Read-onlyIdempotent

State, SA3/SA4, postcode, population, dwellings and centroid for the suburb.

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

Input Schema

NameRequiredDescriptionDefault
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": "Suburb at a glance — geography chain, population, dwellings, centroid.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "dwellings": 2453,
-            "lat": -33.01705,
-            "lng": 151.672252,
-            "population": 6280,
-            "postcode": "2280",
-            "sa3": "Lake Macquarie - East",
-            "sa4": "Newcastle and Lake Macquarie",
-            "state": "New South Wales",
-            "state_abbr": "NSW"
-          },
-          "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"
-            },
-            "dwellings": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Total dwellings (sum over the suburb's mesh blocks, ABS Census).",
-              "title": "Dwellings"
-            },
-            "lat": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Latitude of the suburb boundary's centroid.",
-              "title": "Lat"
-            },
-            "lng": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Longitude of the suburb boundary's centroid.",
-              "title": "Lng"
-            },
-            "population": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Total population (sum over the suburb's mesh blocks, ABS Census).",
-              "title": "Population"
-            },
-            "postcode": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Postcode (POA) covering the suburb.",
-              "title": "Postcode"
-            },
-            "sa3": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "ABS SA3 region the suburb sits in.",
-              "title": "Sa3"
-            },
-            "sa4": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "ABS SA4 region the suburb sits in.",
-              "title": "Sa4"
-            },
-            "state": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "State / territory full name, e.g. 'New South Wales'.",
-              "title": "State"
-            },
-            "state_abbr": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "State / territory abbreviation, e.g. 'NSW'.",
-              "title": "State Abbr"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level"
-          ],
-          "title": "HeroSummary",
-          "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[HeroSummary]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_HeroSummary_"
-}New value: +null
  2. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so safety is not the gap. The description adds two things annotations cannot: the price per call, a genuinely decision-relevant cost trait, and the set of fields returned, which substitutes for the missing output schema. It says nothing about behavior for an unknown or ambiguous suburb name, which is the main remaining blind spot.

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 plus a bolded cost line, with the payload description front-loaded and no filler. The bolding keeps the cost scannable. Nothing could be cut without losing content, though the pricing line could be integrated more smoothly.

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, listing the returned fields is the right compensatory move, and the cost is disclosed. However, for a paid lookup keyed on a free-text parameter, the omission of input format and no-match behavior leaves the agent guessing on the two things most likely to cause a wasted call.

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% for the single required parameter, so the description must compensate and does not. It never states the expected format of suburb_name (bare name, 'Suburb, STATE', or coordinates), nor whether ambiguous names resolve to one result or many.

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 names the resource (suburb) and enumerates exactly what the summary returns: state, SA3/SA4, postcode, population, dwellings, centroid. That field list distinguishes it from the many suburbs_area_stats_* siblings, which each cover a narrow topic. It stops short of an explicit verb or naming a sibling it is meant to replace, so it is clear but not maximally differentiating.

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?

There is no statement of when to call this versus suburbs_hero_neighbours, suburbs_sales_summary, geocode_suburb or any of the area-stats tools, and no prerequisites. The only usage signal is the cost note ('5¢ per call'), which hints at frugality but gives no routing logic.

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