Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Dominant ancestry by mesh block (by suburb)

suburbs_demographics_ancestry_map
Read-onlyIdempotent

The dominant ancestry (and its share) in each of the suburb's mesh blocks, plus suburb-level ancestry shares.

Pilot coverage: about 20 suburbs so far. Anywhere else it answers the no-data 404, which is not billed — so trying a suburb costs nothing.

Price: 20¢ 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_demographics_ancestry_map"
  }
}

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": "Per-microburb dominant ancestry (pilot-coverage dataset).",
-          "example": {
-            "microburbs": [
-              {
-                "dominant_ancestry": "Anglo-Australian",
-                "mb": "10694860000",
-                "persons": 118,
-                "share_pct": 62.1,
-                "street": "Edinburgh Rd"
-              }
-            ],
-            "n_microburbs": 37,
-            "suburb": "Castlecrag",
-            "suburb_ancestry_shares": [
-              {
-                "ancestry": "Anglo-Australian",
-                "pct": 58.4
-              },
-              {
-                "ancestry": "Chinese",
-                "pct": 12.9
-              }
-            ]
-          },
-          "properties": {
-            "microburbs": {
-              "description": "Dominant ancestry per microburb.",
-              "items": {
-                "additionalProperties": true,
-                "description": "One microburb's dominant ancestry.",
-                "properties": {
-                  "dominant_ancestry": {
-                    "description": "Largest ancestry bucket.",
-                    "title": "Dominant Ancestry",
-                    "type": "string"
-                  },
-                  "mb": {
-                    "description": "ABS mesh-block code.",
-                    "title": "Mb",
-                    "type": "string"
-                  },
-                  "persons": {
-                    "anyOf": [
-                      {
-                        "type": "integer"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Total persons in the MB.",
-                    "title": "Persons"
-                  },
-                  "share_pct": {
-                    "description": "Dominant bucket's share of ancestry responses (%).",
-                    "title": "Share Pct",
-                    "type": "number"
-                  },
-                  "street": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Modal street name in the MB.",
-                    "title": "Street"
-                  }
-                },
-                "required": [
-                  "mb",
-                  "dominant_ancestry",
-                  "share_pct"
-                ],
-                "title": "AncestryMb",
-                "type": "object"
-              },
-              "title": "Microburbs",
-              "type": "array"
-            },
-            "n_microburbs": {
-              "description": "Microburbs with ancestry data.",
-              "title": "N Microburbs",
-              "type": "integer"
-            },
-            "suburb": {
-              "description": "Canonical SAL name.",
-              "title": "Suburb",
-              "type": "string"
-            },
-            "suburb_ancestry_shares": {
-              "description": "Suburb-level ancestry shares, descending.",
-              "items": {
-                "additionalProperties": true,
-                "description": "Suburb-level ancestry share.",
-                "properties": {
-                  "ancestry": {
-                    "description": "Ancestry bucket name.",
-                    "title": "Ancestry",
-                    "type": "string"
-                  },
-                  "pct": {
-                    "description": "Share of all ancestry responses (%).",
-                    "title": "Pct",
-                    "type": "number"
-                  }
-                },
-                "required": [
-                  "ancestry",
-                  "pct"
-                ],
-                "title": "AncestryShare",
-                "type": "object"
-              },
-              "title": "Suburb Ancestry Shares",
-              "type": "array"
-            }
-          },
-          "required": [
-            "suburb",
-            "n_microburbs",
-            "microburbs",
-            "suburb_ancestry_shares"
-          ],
-          "title": "SuburbAncestryMap",
-          "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[SuburbAncestryMap]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SuburbAncestryMap_"
-}New value: +null
  2. First observed

TDQS

A3.8/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 and closed-world, so safety is covered. The description adds information the annotations cannot: a 20¢ per-call price and the fact that a no-data miss is free, which directly affects whether an agent should probe an uncertain suburb. It stops short of describing the response shape, which matters since no output schema exists.

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?

The output description is front-loaded in the first sentence and the coverage and pricing caveats follow. Three short blocks with no filler, though the bolded price line reads as a separate marketing note rather than integrated guidance.

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?

For a single-parameter data lookup with no output schema, the description covers what is returned (dominant ancestry and share per mesh block, plus suburb-level shares), the coverage limits, the failure mode, and the cost. The only residual gap is the suburb_name format, which is minor against everything else supplied.

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?

Schema description coverage is 0% — suburb_name is a bare string with no format hint. The description implies the parameter is a suburb identifier and that coverage is limited to ~20 suburbs, but it never specifies expected format (with or without state, suburb vs postcode) or whether matching is fuzzy, so the agent is left guessing on a required input.

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 and granularity: dominant ancestry plus its share for each mesh block in a suburb, with suburb-level shares as a secondary output. That mesh-block granularity distinguishes it from siblings like suburbs_area_stats_ancestry or suburbs_ethnicity_ancestry, though the description never names those alternatives explicitly.

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?

It gives a real usage constraint — pilot coverage of roughly 20 suburbs, with anything else returning a non-billed 404 — which tells an agent when the call will and won't succeed. However, it offers no guidance on choosing this tool over the ancestry area-stats or ethnicity siblings, so the agent must infer the alternative from the name 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 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