Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Capital-growth drivers

suburbs_market_growth_drivers
Read-onlyIdempotent

Per-indicator capital-growth attribution for the suburb.

Each row pairs the suburb's own value for an indicator with the capital-growth differential our matched studies attribute to it, in percentage points. Covers supply & demand pressure, market signals, environmental risks and demographic composition.

Price: 25¢ 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_market_growth_drivers"
  }
}

Input Schema

NameRequiredDescriptionDefault
suburb_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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": "Every capital-growth driver the v6 report attributes to a suburb.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "drivers": [
-              {
-                "band": "(0.999, 1.51]",
-                "basis": "nat_rel",
-                "category": "supply_demand",
-                "direction": "positive",
-                "horizon_years": 2,
-                "impact_pct_per_year": 1.11,
-                "indicator": "Months of Supply",
-                "key": "prop_list_months_of_supply",
-                "source": "thresholds_v3_prod",
-                "unit": "months",
-                "value": 1
-              },
-              {
-                "band": "present",
-                "basis": "matched_control",
-                "category": "risks",
-                "direction": "neutral",
-                "horizon_years": 1,
-                "impact_pct_per_year": -0.29,
-                "indicator": "Contamination",
-                "key": "contamination",
-                "source": "dbyd_matched_cg",
-                "unit": "%",
-                "value": 18.19
-              },
-              {
-                "band": "Top",
-                "basis": "nat_bin",
-                "category": "demographics",
-                "direction": "positive",
-                "horizon_years": 4,
-                "impact_pct_per_year": 0.43,
-                "indicator": "Cultural Integration",
-                "key": "cultural_integration",
-                "source": "cultural_integration_sal",
-                "unit": "score_0_100",
-                "value": 61.8
-              }
-            ]
-          },
-          "properties": {
-            "area_level": {
-              "description": "Always 'suburb' for this endpoint.",
-              "title": "Area Level",
-              "type": "string"
-            },
-            "area_name": {
-              "description": "Suburb (SAL) name.",
-              "title": "Area Name",
-              "type": "string"
-            },
-            "drivers": {
-              "description": "One row per indicator that carries an attributed impact. Indicators with no value for this suburb, or no matching band, are omitted rather than returned as zero.",
-              "items": {
-                "description": "One indicator and the capital-growth differential attributed to it.",
-                "properties": {
-                  "band": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "The band the suburb's value fell into: a numeric interval for threshold-model drivers, 'present'/'absent' for risks, or the tier name for cultural integration.",
-                    "title": "Band"
-                  },
-                  "basis": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Control group the differential is relative to: 'nat_rel' (national), 'gccsa_rel' (capital-city region), 'nat_bin' (national tier), 'matched_control' (matched address pairs).",
-                    "title": "Basis"
-                  },
-                  "category": {
-                    "description": "Report section the driver belongs to: 'supply_demand', 'market', 'risks' or 'demographics'.",
-                    "title": "Category",
-                    "type": "string"
-                  },
-                  "direction": {
-                    "description": "'positive', 'negative' or 'neutral' — the tone the report gives the chip.",
-                    "title": "Direction",
-                    "type": "string"
-                  },
-                  "horizon_years": {
-                    "anyOf": [
-                      {
-                        "type": "integer"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Window the differential was measured over. Threshold-model studies run 2 or 4 years and the report presents the raw differential as an annual rate; the cultural-integration model annualises its 4-year figure first; risk coefficients are already per-year.",
-                    "title": "Horizon Years"
-                  },
-                  "impact_pct_per_year": {
-                    "description": "Capital-growth differential attributed to this indicator, in percentage points, exactly as the report renders it.",
-                    "title": "Impact Pct Per Year",
-                    "type": "number"
-                  },
-                  "indicator": {
-                    "description": "Human label, matching the report's row label.",
-                    "title": "Indicator",
-                    "type": "string"
-                  },
-                  "key": {
-                    "description": "Stable machine identifier for the indicator.",
-                    "title": "Key",
-                    "type": "string"
-                  },
-                  "source": {
-                    "description": "Model the row came from: 'thresholds_v3_prod', 'dbyd_matched_cg' or 'cultural_integration_sal'.",
-                    "title": "Source",
-                    "type": "string"
-                  },
-                  "unit": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Unit of `value` — e.g. 'months', 'fraction', 'AUD', '%', 'ANEF', 'score_0_100'.",
-                    "title": "Unit"
-                  },
-                  "value": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "The suburb's own value for this indicator (see `unit`).",
-                    "title": "Value"
-                  }
-                },
-                "required": [
-                  "category",
-                  "key",
-                  "indicator",
-                  "direction",
-                  "impact_pct_per_year",
-                  "source"
-                ],
-                "title": "GrowthDriver",
-                "type": "object"
-              },
-              "title": "Drivers",
-              "type": "array"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "drivers"
-          ],
-          "title": "GrowthDrivers",
-          "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[GrowthDrivers]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_GrowthDrivers_"
-}New value: +null
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description correctly spends its space elsewhere: it discloses cost ('25¢ per call') and describes the returned row structure and the four indicator families covered. Pricing and output-shape disclosure are genuinely extra behavioral context annotations cannot supply.

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 clauses with the core purpose front-loaded and the return shape immediately after; the price line is a separate, useful callout. Slightly abstract phrasing ('our matched studies') costs a little clarity but nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by explaining what each row contains and what the differential is measured in, plus coverage of the indicator categories. The only substantial omission is input-format guidance for suburb_name.

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?

The single parameter suburb_name has zero schema description coverage, and the description adds no format or expectation guidance (e.g., whether state/postcode is required, whether a geocoded ID works). A sibling like geocode_suburb implies disambiguation matters, so leaving the input format unstated is a real gap.

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 names a specific resource and analysis ('per-indicator capital-growth attribution for the suburb') and even describes the row shape: indicator value paired with an attributed differential in percentage points. It clearly distinguishes itself from price-level siblings such as suburbs_market_price_growth by framing output as attribution, though it never names an alternative or contrast, so a 4 rather than 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 implied by the content ('each row pairs...'), suggesting this is the tool for decomposing which factors drive growth in one suburb, but there is no explicit when-to-use or when-not-to-use statement. Given the crowded sibling set including suburbs_risks_capital_growth_impact, a routing hint would have materially helped.

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 toolsInspect
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