Microburbs Australian Property Data

Suburb · Ancestry breakdown

suburbs_ethnicity_ancestry

Read-onlyIdempotent

Ancestry breakdown from the ABS census.

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": [
-        {
-          "items": {
-            "additionalProperties": true,
-            "description": "One row of ancestry / birthplace data.",
-            "example": {
-              "ancestry": "Australians",
-              "area_level": "suburb",
-              "area_name": "Belmont North",
-              "proportion": 0.926304347826087
-            },
-            "properties": {
-              "ancestry": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Only on /ethnicity/ancestry.",
-                "title": "Ancestry"
-              },
-              "area_level": {
-                "description": "Always 'suburb'.",
-                "title": "Area Level",
-                "type": "string"
-              },
-              "area_name": {
-                "description": "Suburb (SAL) name.",
-                "title": "Area Name",
-                "type": "string"
-              },
-              "birthplace": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Only on /ethnicity/birthplace.",
-                "title": "Birthplace"
-              },
-              "proportion": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Share of the suburb identifying with this category (0–1).",
-                "title": "Proportion"
-              }
-            },
-            "required": [
-              "area_name",
-              "area_level"
-            ],
-            "title": "EthnicityRow",
-            "type": "object"
-          },
-          "type": "array"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "The endpoint's payload, or `null` when Microburbs has no value.",
-      "title": "Data"
-    },
-    "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[list[EthnicityRow]]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_list_EthnicityRow__"
-}New value: +null

First observedSep 14, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds only the ABS census provenance; it does not disclose behavioral traits like census year coverage, grouping/percentage format, or any limitations of the breakdown.

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 description is a single efficient sentence with no filler. It is front-loaded and easy to parse, though it is brief enough that it verges on under-specification; that shortfall is better counted in other dimensions.

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 simple read-only tool with one obvious parameter, the description is minimally viable: it identifies the resource and source, and annotations cover safety. However, there is no output schema, so the description should clarify what shape the ancestry breakdown takes and how it differs from the sibling ethnicity tools; it does not.

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%, so the description should compensate for the sole required parameter, suburb_name. It never mentions the parameter, its expected format, or how to obtain valid suburb names. The schema only says 'string', which is minimal.

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

Purpose3/5

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

The description says the tool returns an 'Ancestry breakdown from the ABS census,' which names the resource and data source. However, it largely restates the title ('Suburb · Ancestry breakdown') and does not distinguish this from nearby siblings like suburbs_ethnicity_all, suburbs_ethnicity_birthplace, or suburbs_demographics_ancestry_map.

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 guidance on when to choose this tool over the many other ethnicity/demographics siblings. No alternatives are named, no exclusions are given, and no context such as 'use this for a focused ancestry view vs. the all-in-one ethnicity tool' is provided.

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?