Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Built Year (by suburb)

suburbs_market_built_year
Read-onlyIdempotent

Shown in the suburb report as the 'Built Year' card in the Market section.

Estimated build-year profile — suburb aggregate + per-mesh-block medians.

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

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": "Suburb build-year aggregate + per-mesh-block medians.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "mbs": [
-              {
-                "mb": "10439043000",
-                "median_yr": 1991,
-                "modal_era": "1980_1999",
-                "n_props": 61,
-                "p10_yr": 1980,
-                "p90_yr": 2000
-              }
-            ],
-            "median_yr": 1979,
-            "modal_era": "1980_1999",
-            "n_mbs": 78,
-            "n_props": 3405,
-            "p10_yr": 1955,
-            "p90_yr": 2010
-          },
-          "properties": {
-            "area_level": {
-              "description": "Always 'suburb' for these endpoints.",
-              "title": "Area Level",
-              "type": "string"
-            },
-            "area_name": {
-              "description": "Suburb (SAL) name.",
-              "title": "Area Name",
-              "type": "string"
-            },
-            "mbs": {
-              "description": "Per-mesh-block estimates.",
-              "items": {
-                "description": "Build-year estimates for one mesh block (FAMOUS model).",
-                "properties": {
-                  "mb": {
-                    "description": "ABS mesh-block code (MB_CODE21).",
-                    "title": "Mb",
-                    "type": "string"
-                  },
-                  "median_yr": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Median estimated build year for the mesh block, rounded to a whole year (typed float for backwards compatibility, so it serialises as 2006.0). An interpolated percentile — a mesh block has no single true build year, so read it as the middle of its range.",
-                    "title": "Median Yr"
-                  },
-                  "modal_era": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Modal era label, e.g. '1980_1999'.",
-                    "title": "Modal Era"
-                  },
-                  "n_props": {
-                    "anyOf": [
-                      {
-                        "type": "integer"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Properties behind the estimate.",
-                    "title": "N Props"
-                  },
-                  "p10_yr": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "10th-percentile build year — 10% of dwellings here are older. Whole years.",
-                    "title": "P10 Yr"
-                  },
-                  "p90_yr": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "90th-percentile build year — 10% of dwellings here are newer. Whole years.",
-                    "title": "P90 Yr"
-                  }
-                },
-                "required": [
-                  "mb"
-                ],
-                "title": "BuiltYearMb",
-                "type": "object"
-              },
-              "title": "Mbs",
-              "type": "array"
-            },
-            "median_yr": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Suburb median build year (median of MB medians).",
-              "title": "Median Yr"
-            },
-            "modal_era": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Dominant era label across MBs, e.g. '1980_1999'.",
-              "title": "Modal Era"
-            },
-            "n_mbs": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Mesh blocks with build-year data.",
-              "title": "N Mbs"
-            },
-            "n_props": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Total properties behind the aggregate.",
-              "title": "N Props"
-            },
-            "p10_yr": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Earliest MB 10th-percentile year (range floor).",
-              "title": "P10 Yr"
-            },
-            "p90_yr": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Latest MB 90th-percentile year (range ceiling).",
-              "title": "P90 Yr"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "mbs"
-          ],
-          "title": "BuiltYear",
-          "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[BuiltYear]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_BuiltYear_"
-}New value: +null
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already cover readOnly, idempotent, non-destructive and closed-world semantics, so the bar is lower. The description still adds two things those fields cannot convey: a per-call cost of 20¢ (relevant to calling it repeatedly or across many suburbs) and the fact that the values are estimates returned at two granularities. It says nothing about missing data or the shape of the per-mesh-block payload, but the pricing disclosure is meaningful added context.

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 with no filler; the card/report mapping, the payload description and the price each earn their place. Leading with the UI card location is slightly less useful than leading with the operation, but nothing is wasted.

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?

With no output schema, the description does mention the return granularities (suburb aggregate and per-mesh-block medians), which helps. However, for a paid, single-parameter lookup it leaves gaps an agent must resolve: the required format of suburb_name, the units of build year, and behaviour for suburbs lacking mesh-block data.

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 0% schema description coverage, so the description carries the full burden and does not pick it up. It never states whether the value is a suburb name string, a postcode-qualified name, an ID, or how exact matching works. An agent has to guess at the input format before spending 20¢ on a call.

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 the resource concretely: an estimated build-year profile, delivered as a suburb aggregate plus per-mesh-block medians. That is more specific than a title restatement, and the 'Built Year' card framing pins the resource down. It stops short of explicitly contrasting with siblings such as suburbs_market_all or suburbs_area_stats_year_of_arrival.

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?

The 'Shown in the suburb report as the Built Year card in the Market section' line implies when the tool is relevant, i.e. when reproducing that report section. There is no explicit when-not guidance, no statement about preconditions, and no signposting of the overlapping alternatives among the market sibling tools.

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