suburbs_market_median_price_mapMedian house price for every microburb (mesh block) in the suburb, with
its modal street name, plus the dearest and cheapest pockets. Values only —
the matching polygons come from /shapes/mesh-blocks.
| 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": "Per-microburb median house price — the report's `mb_price` overlay.",
- "example": {
- "as_of": "2026-08-09",
- "definition": "Modelled median (50th-percentile) house price for the mesh block, from the modelled per-microburb price surface. Mesh block = 'microburb', the smallest ABS geography (~30-60 dwellings). Mesh blocks with too little signal are absent rather than zero.",
- "highest": {
- "mb": "10434032000",
- "median_price": 3843000,
- "street": "Pacific"
- },
- "lowest": {
- "mb": "10439043000",
- "median_price": 625900,
- "street": "Lentara"
- },
- "metric": "median_house_price",
- "microburbs": [
- {
- "mb": "10434032000",
- "median_price": 3843000,
- "street": "Pacific"
- }
- ],
- "n_microburbs": 63,
- "suburb": "Belmont North",
- "unit": "AUD"
- },
- "properties": {
- "as_of": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Date of the price surface (YYYY-MM-DD).",
- "title": "As Of"
- },
- "definition": {
- "description": "How the figure is derived.",
- "title": "Definition",
- "type": "string"
- },
- "highest": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "Median house price for one microburb (mesh block).",
- "properties": {
- "mb": {
- "description": "ABS 2021 mesh-block code.",
- "title": "Mb",
- "type": "string"
- },
- "median_price": {
- "description": "Median house price, AUD.",
- "title": "Median Price",
- "type": "integer"
- },
- "street": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Modal street name for the mesh block, title-cased.",
- "title": "Street"
- }
- },
- "required": [
- "mb",
- "median_price"
- ],
- "title": "MedianPriceMb",
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "description": "Dearest microburb. None when there is no spread."
- },
- "lowest": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "Median house price for one microburb (mesh block).",
- "properties": {
- "mb": {
- "description": "ABS 2021 mesh-block code.",
- "title": "Mb",
- "type": "string"
- },
- "median_price": {
- "description": "Median house price, AUD.",
- "title": "Median Price",
- "type": "integer"
- },
- "street": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Modal street name for the mesh block, title-cased.",
- "title": "Street"
- }
- },
- "required": [
- "mb",
- "median_price"
- ],
- "title": "MedianPriceMb",
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "description": "Cheapest microburb. None when there is no spread."
- },
- "metric": {
- "description": "Always 'median_house_price'.",
- "title": "Metric",
- "type": "string"
- },
- "microburbs": {
- "description": "Per-microburb prices, highest first.",
- "items": {
- "additionalProperties": true,
- "description": "Median house price for one microburb (mesh block).",
- "properties": {
- "mb": {
- "description": "ABS 2021 mesh-block code.",
- "title": "Mb",
- "type": "string"
- },
- "median_price": {
- "description": "Median house price, AUD.",
- "title": "Median Price",
- "type": "integer"
- },
- "street": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Modal street name for the mesh block, title-cased.",
- "title": "Street"
- }
- },
- "required": [
- "mb",
- "median_price"
- ],
- "title": "MedianPriceMb",
- "type": "object"
- },
- "title": "Microburbs",
- "type": "array"
- },
- "n_microburbs": {
- "description": "Microburbs with a price.",
- "title": "N Microburbs",
- "type": "integer"
- },
- "suburb": {
- "description": "Canonical SAL name.",
- "title": "Suburb",
- "type": "string"
- },
- "unit": {
- "description": "Always 'AUD'.",
- "title": "Unit",
- "type": "string"
- }
- },
- "required": [
- "suburb",
- "metric",
- "unit",
- "definition",
- "n_microburbs",
- "microburbs"
- ],
- "title": "SuburbMedianPriceMap",
- "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[SuburbMedianPriceMap]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_SuburbMedianPriceMap_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and non-destructive, so the bar is lower. The description adds valuable behavioral context beyond annotations: output is values only and geometry must be joined from another endpoint, plus the output includes modal street name and extreme pockets.
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?
Two sentences, front-loaded with the core purpose, and every clause earns its place. The 'Values only' caveat is essential and placed at the end for clarity without burying the main function.
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?
For a single-parameter tool with no output schema, the description covers the output contents, granularity, and the geometry source. It stops short of describing exact response fields or formatting, but the essential information needed to call and interpret the tool is present.
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?
There is one parameter, suburb_name, with no schema description. The description references 'the suburb' implicitly, giving some context, and the parameter name is self-explanatory. However, it does not explain accepted formats, identifier styles, or case sensitivity, so it does not fully compensate for the 0% schema coverage.
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?
States exactly what the tool returns: median house price per microburb/mesh block, modal street name, and dearest/cheapest pockets. It also distinguishes itself from shape-returning tools by explicitly saying 'Values only' and pointing to the polygon source.
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?
Clearly implies when to use this tool (per-microburb median house price values) and gives an explicit exclusion: if polygons are needed, use /shapes/mesh-blocks. It does not explicitly compare to sibling median-sale-price or rent-map tools, but the scope is clear enough to avoid the most obvious confusion.
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.