Microburbs Australian Property Data

Suburb · All ethnicity — bundle

suburbs_ethnicity_all

Read-onlyIdempotent

All ethnicity — bundle

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": [
-        {
-          "properties": {
-            "ancestry": {
-              "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"
-                }
-              ],
-              "title": "Ancestry"
-            },
-            "birthplace": {
-              "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"
-                }
-              ],
-              "title": "Birthplace"
-            }
-          },
-          "title": "EthnicityAll",
-          "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[EthnicityAll]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_EthnicityAll_"
-}New value: +null

First observedSep 14, 2026

TDQS

D1.1/5.0

Behavior1/5

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

The description adds no behavioral information beyond the annotations. While annotations declare readOnlyHint=true and idempotentHint=true, the description does not explain what 'all ethnicity' contains, what fields are returned, or any limitations. For a bundle tool with no output schema, this is a severe gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief (three words), but this is under-specification, not conciseness. It lacks a sentence structure and fails to convey any actionable information, similar to the 'Process' example in the calibration guidelines.

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

Completeness1/5

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

With no output schema and no description of the returned bundle, the tool is completely underspecified. Given the large sibling list and granular ethnicity alternatives, the agent cannot determine what this tool provides or whether it is the right choice.

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

Parameters1/5

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

Schema description coverage is 0% and the description says nothing about the 'suburb_name' parameter. It does not clarify expected format, whether it accepts full names or codes, or any constraints. The description fails entirely to compensate for the missing schema documentation.

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

Purpose1/5

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

The description 'All ethnicity — bundle' is a tautology that restates the title 'Suburb · All ethnicity — bundle'. It uses no verb or resource, and gives no indication of what data is returned. It does not distinguish itself from sibling tools like suburbs_ethnicity_ancestry or suburbs_ethnicity_birthplace.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus the ethnicity-specific siblings. No mention of context, exclusions, or alternative tools. The agent would have to guess whether to call this bundle or the more granular ancestry/birthplace variants.

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?