Microburbs Australian Property Data

Suburb · Single Parents

suburbs_demographics_single_parents

Read-onlyIdempotent

Shown in the suburb report as the 'Single Parents' card in the Demographics section.

Single-parent-family share for the suburb against the pinned national median, with the associated capital-growth impact.

Price: 3¢ 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_single_parents"
  }
}

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": "Single-parent-family share vs the national median.",
-          "example": {
-            "growth_impact": {
-              "band": "High single-parent share",
-              "pct_per_year": -0.5
-            },
-            "national_median_pct": 5.8,
-            "single_parent_pct": 11,
-            "suburb": "Belmont North",
-            "vs_national": "above"
-          },
-          "properties": {
-            "growth_impact": {
-              "additionalProperties": true,
-              "description": "The capital-growth difference historically associated with suburbs in this single-parent-share band. An association, not a forecast — see the field's own description.",
-              "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"
-            },
-            "national_median_pct": {
-              "description": "The Australia-wide single-parent-family share to compare `single_parent_pct` against, as a percentage — a fixed 2021 Census benchmark, identical in every response. A different metric and a different number from the unemployment endpoint's benchmark of the same name.",
-              "title": "National Median Pct",
-              "type": "number"
-            },
-            "single_parent_pct": {
-              "description": "Single-parent-family share as a percentage.",
-              "title": "Single Parent Pct",
-              "type": "number"
-            },
-            "suburb": {
-              "description": "Canonical SAL name.",
-              "title": "Suburb",
-              "type": "string"
-            },
-            "vs_national": {
-              "description": "Whether this suburb's single-parent share sits 'below' or 'above' the national benchmark. Exact equality is reported as 'above'.",
-              "enum": [
-                "below",
-                "above"
-              ],
-              "title": "Vs National",
-              "type": "string"
-            }
-          },
-          "required": [
-            "suburb",
-            "single_parent_pct",
-            "national_median_pct",
-            "vs_national",
-            "growth_impact"
-          ],
-          "title": "SingleParents",
-          "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[SingleParents]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SingleParents_"
-}New value: +null

First observedSep 14, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds genuinely useful non-annotation context: a per-call cost of 3¢ and the fact that the value is benchmarked against a pinned national median with a capital-growth interpretation, but it says nothing about failure behavior for unknown suburbs or how fresh the pinned median is.

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?

Two compact statements: what the metric is and where it surfaces, then the cost. Front-loaded and free of filler, though the UI-placement sentence is the weakest earner since it informs presentation rather than invocation.

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, and the description partially compensates by describing the returned shape (local share versus national median plus a capital-growth impact). It remains incomplete for a data-lookup tool because the single input's format and the behavior on missing or ambiguous suburbs are undocumented.

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 carries the full burden for the single required parameter, yet it never states the expected format of suburb_name (bare name, 'Suburb, STATE', postcode-qualified, or an internal ID) nor whether ambiguity or non-matches error out. With only one parameter and zero schema documentation, this is a real gap rather than a minor omission.

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 verb+resource: single-parent-family share for a suburb measured against the pinned national median, plus associated capital-growth impact. That is more specific than the title, and it clearly differs from a mapping/visualization sibling, though it never names the *_map variant as the alternative to use for spatial output.

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?

The only usage framing is placement in the product UI ('Shown in the suburb report as the Single Parents card in the Demographics section'), which tells the agent where the number appears, not when to call this tool instead of suburbs_demographics_all, the map variant, or a broader profile tool. No prerequisites, no exclusions, no alternative routing.

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?