Microburbs Australian Property Data

Suburb · Age-bracket breakdown

suburbs_demographics_age

Read-onlyIdempotent

Population by age bracket and gender.

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 demographic data — age bracket or income bracket. The\nshape varies per endpoint; common keys are always present, the rest\nare open (``extra=allow``) so a renamed sub-key doesn't break\nclients.",
-            "example": {
-              "age_bracket": "0-4",
-              "area_level": "suburb",
-              "area_name": "Belmont North",
-              "gender": "females",
-              "proportion": 0.0272
-            },
-            "properties": {
-              "age_bracket": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Only on /demographics/age.",
-                "title": "Age Bracket"
-              },
-              "area_level": {
-                "description": "Always 'suburb'.",
-                "title": "Area Level",
-                "type": "string"
-              },
-              "area_name": {
-                "description": "Suburb (SAL) name.",
-                "title": "Area Name",
-                "type": "string"
-              },
-              "gender": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Only on /demographics/age — 'males' / 'females' / 'persons'.",
-                "title": "Gender"
-              },
-              "income_bracket": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Only on /demographics/income.",
-                "title": "Income Bracket"
-              },
-              "median_income": {
-                "anyOf": [
-                  {
-                    "type": "integer"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Only on /demographics/income.",
-                "title": "Median Income"
-              },
-              "proportion": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Share of the suburb in this bracket (0–1).",
-                "title": "Proportion"
-              }
-            },
-            "required": [
-              "area_name",
-              "area_level"
-            ],
-            "title": "DemographicRow",
-            "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[DemographicRow]]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_list_DemographicRow__"
-}New value: +null

First observedSep 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the specific dimensions (age bracket and gender) but doesn't disclose anything beyond that, such as whether the data is census-based, what age brackets are used, or how gender is categorized. With annotations covering the safety profile, a 3 is appropriate.

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 concise sentence that front-loads the key information: population by age bracket and gender. It's appropriately sized for a simple tool with one parameter. It could add a bit more context (e.g., data source or typical use), but it's not bloated or redundant.

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 parameter and no output schema, the description is mostly adequate. It tells the agent what data it will get (age bracket and gender breakdown). However, it doesn't mention the output format, whether the data is a single aggregate or per-gender rows, or any caveats like data availability for small suburbs. Given the tool's simplicity, this is a minor gap, so 3.

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%, so the description must compensate for the single parameter suburb_name. The description doesn't explain that suburb_name is the required input or what format it should take (e.g., 'Sydney' vs 'Sydney, NSW'). However, with only one parameter and a clear name, the schema is self-explanatory. The description adds no parameter-level detail, so baseline 3 is fair.

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 'Population by age bracket and gender' clearly states the resource (suburb population) and the specific breakdown (age bracket and gender). It distinguishes itself from sibling tools like suburbs_demographics_all and suburbs_demographics_income by naming the exact demographic dimensions. However, it doesn't explicitly mention the suburb_name parameter or contrast with a specific sibling, so it's not a 5.

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?

The description implies usage: call this when you need age-bracket and gender population data for a suburb. It doesn't explicitly state when to use this vs alternatives like suburbs_demographics_all or suburbs_demographics_cohorts, but the title and description make the niche clear. No exclusions or alternative routing are provided, so it's a 3.

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?