Microburbs Australian Property Data

by au.com.microburbs

Overview Discussions Admin

Private School Students (by suburb)

suburbs_demographics_private_school

Read-onlyIdempotent

Shown in the suburb report as the 'Private School Students' card in the Demographics section.

Share of residents attending Catholic / Independent schools — suburb rollup plus the per-mesh-block shares behind it.

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_private_school"
  }
}

Input 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": [
-        {
-          "additionalProperties": true,
-          "description": "Share of residents attending Catholic / Independent schools.",
-          "example": {
-            "basis": "microburb_downscale",
-            "growth_impact": {
-              "band": "Low private-school share",
-              "pct_per_year": -0.3
-            },
-            "microburbs": [
-              {
-                "mb": "10664530000",
-                "private_school_pct": 5.8,
-                "street": "Marquis St"
-              }
-            ],
-            "n_microburbs": 71,
-            "private_school_pct": 4.7,
-            "suburb": "Belmont North"
-          },
-          "properties": {
-            "basis": {
-              "description": "How private_school_pct was derived — 'microburb_downscale' (mesh-block share rollup, preferred) or 'census_count_over_population' (suburb census student count over mesh-block population).",
-              "enum": [
-                "microburb_downscale",
-                "census_count_over_population"
-              ],
-              "title": "Basis",
-              "type": "string"
-            },
-            "growth_impact": {
-              "additionalProperties": true,
-              "description": "Capital-growth impact associated with the share band.",
-              "properties": {
-                "band": {
-                  "description": "Plain-language name of the band the suburb landed in, suitable for display alongside the figure — e.g. 'Middle 90%', 'High unemployment', 'Low private-school share'. The wording differs per indicator; treat it as a label, not a shared enum.",
-                  "title": "Band",
-                  "type": "string"
-                },
-                "pct_per_year": {
-                  "description": "The growth difference historically associated with this band, in percentage points per year on a percent scale — `-3.8` means 3.8 percentage points a year worse, `0.5` means half a point a year better, and `0.0` (the common case, for suburbs in the middle band) means no association either way. A relative difference, not a growth rate in its own right.",
-                  "title": "Pct Per Year",
-                  "type": "number"
-                }
-              },
-              "required": [
-                "pct_per_year",
-                "band"
-              ],
-              "title": "GrowthImpact",
-              "type": "object"
-            },
-            "microburbs": {
-              "description": "Per-mesh-block private-school shares (sparse cells dropped).",
-              "items": {
-                "additionalProperties": true,
-                "description": "One mesh block's private-school share.",
-                "properties": {
-                  "mb": {
-                    "description": "ABS mesh-block code.",
-                    "title": "Mb",
-                    "type": "string"
-                  },
-                  "private_school_pct": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Downscaled private-school share for the mesh block.",
-                    "title": "Private School Pct"
-                  },
-                  "street": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Modal street name in the mesh block.",
-                    "title": "Street"
-                  }
-                },
-                "required": [
-                  "mb"
-                ],
-                "title": "PrivateSchoolMicroburb",
-                "type": "object"
-              },
-              "title": "Microburbs",
-              "type": "array"
-            },
-            "n_microburbs": {
-              "description": "Mesh blocks in the microburbs list.",
-              "title": "N Microburbs",
-              "type": "integer"
-            },
-            "private_school_pct": {
-              "description": "Share of residents attending Catholic / Independent schools, as a percentage.",
-              "title": "Private School Pct",
-              "type": "number"
-            },
-            "suburb": {
-              "description": "Canonical SAL name.",
-              "title": "Suburb",
-              "type": "string"
-            }
-          },
-          "required": [
-            "suburb",
-            "private_school_pct",
-            "basis",
-            "growth_impact",
-            "n_microburbs",
-            "microburbs"
-          ],
-          "title": "PrivateSchool",
-          "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[PrivateSchool]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_PrivateSchool_"
-}New value: +null

First observedSep 14, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description's real contribution is the pricing disclosure ('20¢ per call'), which is valuable operational context an agent cannot get from annotations, but it says nothing about permissions, response shape, or units of the share figure.

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?

Three short lines, front-loaded with the card context then the actual data definition, with the cost stated last as a distinct note. The 'shown in the suburb report' framing is mildly meta but cheap and orients the caller.

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?

No output schema exists, so the description must carry return-value meaning; it identifies the two levels of aggregation but not the units (percentage vs. count), which schools count as 'Independent', or the mesh-block granularity definition. For a paid, single-parameter data tool this is adequate but leaves gaps an agent would want closed.

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?

There is one required parameter, suburb_name, with 0% schema description coverage, and the description never mentions it. It does not state the expected format (plain name vs. name plus state, or an ID) or how ambiguous or duplicate suburb names resolve – a real risk for Australian suburb data – so the coverage gap is not compensated.

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?

States a concrete measure ('share of residents attending Catholic / Independent schools') and the granularity delivered ('suburb rollup plus the per-mesh-block shares behind it'). It does not distinguish itself from the many other suburbs_demographics_* tools beyond topic naming, so it falls short of 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?

Usage is only implied – the agent can infer this is the demographics card for private-school attendance, and that it returns block-level detail as well as a rollup. There is no explicit when-to-use guidance, no statement of when to prefer suburbs_demographics_all or a related sibling, and no prerequisites or exclusions.

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?