suburbs_ethnicity_allCultural make-up of the suburb from the census: ancestry breakdown and country of birth, each as a share of residents.
Useful for understanding who a suburb's buyers and renters are. The map version, which splits these by mesh block, is a separate call.
| Name | Required | Description | Default |
|---|---|---|---|
| suburb_name | Yes |
Changes observed during successful MCP inspections.
Output 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: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, non-open-world semantics, so the safety profile is covered. The description adds that results are census-derived shares of residents, but says nothing about geography level, refresh cadence, or what happens if the suburb is unknown.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with what is returned before the use case and the alternative-call note. No filler; slightly more could be said given the 0% schema coverage.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-output-schema read tool over a single obvious key, the description names the returned metrics (ancestry, country of birth, as resident shares) and distinguishes the mesh-block alternative. Nothing an agent needs to select or invoke it is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
One parameter with 0% schema description coverage, and the description adds no formatting guidance for suburb_name (postcode? exact name? case?). The parameter is self-evident for anyone familiar with the sibling suburb tools, so this is adequate but uncompensated.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource (census ancestry + country-of-birth shares for a suburb) with a clear bundled scope. It implicitly differentiates from the split siblings suburbs_ethnicity_ancestry/birthplace via the 'bundle' framing, though it never names them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives a use case ('understanding who a suburb's buyers and renters are') and rules out the mesh-block map variant as 'a separate call'. It stops short of telling the agent when to prefer the single ancestry or birthplace siblings over this bundle.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.