suburbs_demographics_cultural_integrationSuburb cultural-integration composite (0-100) with national percentile and tier, plus the per-microburb scores behind it.
| 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": [
- {
- "additionalProperties": true,
- "description": "Cultural-integration composite — suburb tier + per-microburb scores.",
- "example": {
- "cg_impact_pct_yr": 0.43,
- "least_integrated": {
- "score_100": 51.5,
- "street": "Kalaroo Rd"
- },
- "microburbs": [
- {
- "mb": "10664530000",
- "score_100": 68.2,
- "street": "Marquis St"
- }
- ],
- "most_integrated": {
- "score_100": 68.2,
- "street": "Marquis St"
- },
- "n_microburbs": 77,
- "percentile": 79.7,
- "score_100": 61.8,
- "suburb": "Belmont North",
- "tier": "Top",
- "tier_growth_pct_4y": 1.7
- },
- "properties": {
- "cg_impact_pct_yr": {
- "description": "Capital-growth impact, % per year (tier growth / 4).",
- "title": "Cg Impact Pct Yr",
- "type": "number"
- },
- "least_integrated": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "Most/least-integrated pocket callout.",
- "properties": {
- "score_100": {
- "description": "Composite score, 0-100.",
- "title": "Score 100",
- "type": "number"
- },
- "street": {
- "description": "Modal street of the pocket's MB.",
- "title": "Street",
- "type": "string"
- }
- },
- "required": [
- "street",
- "score_100"
- ],
- "title": "IntegrationPocket",
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "description": "Lowest-scoring pocket."
- },
- "microburbs": {
- "description": "Per-microburb composite scores.",
- "items": {
- "additionalProperties": true,
- "description": "One microburb's cultural-integration composite.",
- "properties": {
- "mb": {
- "description": "ABS mesh-block code.",
- "title": "Mb",
- "type": "string"
- },
- "score_100": {
- "description": "Composite score, 0-100.",
- "title": "Score 100",
- "type": "number"
- },
- "street": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Modal street name in the MB.",
- "title": "Street"
- }
- },
- "required": [
- "mb",
- "score_100"
- ],
- "title": "CulturalIntegrationMb",
- "type": "object"
- },
- "title": "Microburbs",
- "type": "array"
- },
- "most_integrated": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "Most/least-integrated pocket callout.",
- "properties": {
- "score_100": {
- "description": "Composite score, 0-100.",
- "title": "Score 100",
- "type": "number"
- },
- "street": {
- "description": "Modal street of the pocket's MB.",
- "title": "Street",
- "type": "string"
- }
- },
- "required": [
- "street",
- "score_100"
- ],
- "title": "IntegrationPocket",
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "description": "Highest-scoring pocket."
- },
- "n_microburbs": {
- "description": "Microburbs with a composite score.",
- "title": "N Microburbs",
- "type": "integer"
- },
- "percentile": {
- "description": "National percentile (0-100).",
- "title": "Percentile",
- "type": "number"
- },
- "score_100": {
- "description": "Suburb composite score, 0-100.",
- "title": "Score 100",
- "type": "number"
- },
- "suburb": {
- "description": "Canonical SAL name.",
- "title": "Suburb",
- "type": "string"
- },
- "tier": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Tier bin: Top / Mid / Bottom.",
- "title": "Tier"
- },
- "tier_growth_pct_4y": {
- "description": "The tier's 4-year price growth (%).",
- "title": "Tier Growth Pct 4Y",
- "type": "number"
- }
- },
- "required": [
- "suburb",
- "score_100",
- "percentile",
- "tier_growth_pct_4y",
- "cg_impact_pct_yr",
- "n_microburbs",
- "microburbs"
- ],
- "title": "SuburbCulturalIntegration",
- "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[SuburbCulturalIntegration]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_SuburbCulturalIntegration_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this tool read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds useful behavioral context by enumerating exactly what is returned: the composite score, national percentile and tier, and the underlying per-microburb scores. It does not contradict annotations.
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?
The description is one tight sentence that front-loads the core resource and immediately states the output structure. Every clause adds information: the 0-100 scale, percentile/tier, and the per-microburb detail. There is no filler or redundancy.
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?
With no output schema, the description correctly enumerates the returned fields and scale, so an agent knows what to expect. For a single-parameter read-only lookup, this is nearly complete. It could optionally clarify edge cases like unknown suburbs or data availability, but those are minor gaps.
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?
Schema description coverage is 0%, so the description carries the burden of explaining parameters, but it does not. The single parameter suburb_name is self-describing, yet there is no guidance on accepted formats (e.g., 'Sydney' vs 'Sydney, NSW') or how it maps to results. The description adds no meaning beyond the schema property name.
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?
The description clearly identifies the tool's subject—a suburb cultural-integration composite with a 0-100 score, national percentile, tier, and per-microburb components. This uniquely distinguishes it from sibling demographics and ethnicity tools by topic. It lacks an explicit retrieval verb, but the resource and output characteristics are unmistakable.
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?
Usage context is implied through the tool name and title: if the user wants a cultural-integration score for a suburb, this is the tool. However, it does not explicitly state when to prefer this over related siblings like suburbs_demographics_all or suburbs_ethnicity_all, nor does it describe any exclusions or prerequisites.
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.