Microburbs Australian Property Data

Property · Council land values — 5-year series

properties_valuation_land_values

Read-onlyIdempotent

Council land valuations for the parcel — val_2021..val_2025 series with YoY change and $/sqm, plus lot area and zoning description. Held for NSW houses (and other whole-lot parcels) only; units and other states return no data.

Price: 15¢ 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": {
      "gnaf_id": "<gnaf_id>"
    },
    "name": "properties_valuation_land_values"
  }
}

Input Schema

Name	Required	Description	Default
`gnaf_id`	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": "Council land valuations for the parcel — 5-year series + lot area + zoning.",
-          "example": {
-            "area_sqm": 714.5,
-            "history": [
-              {
-                "price_per_sqm": 2449.27,
-                "value": 1750000,
-                "year": 2021
-              },
-              {
-                "price_per_sqm": 3177.05,
-                "value": 2270000,
-                "year": 2022,
-                "yoy_pct": 29.71
-              },
-              {
-                "price_per_sqm": 2883.14,
-                "value": 2060000,
-                "year": 2023,
-                "yoy_pct": -9.25
-              },
-              {
-                "price_per_sqm": 3177.05,
-                "value": 2270000,
-                "year": 2024,
-                "yoy_pct": 10.19
-              },
-              {
-                "price_per_sqm": 3177.05,
-                "value": 2270000,
-                "year": 2025,
-                "yoy_pct": 0
-              }
-            ],
-            "land_value": 2270000,
-            "zone_desc": "C4 - Environmental Living"
-          },
-          "properties": {
-            "area_sqm": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Lot area (square metres).",
-              "title": "Area Sqm"
-            },
-            "history": {
-              "description": "Per-year valuation series, oldest first.",
-              "items": {
-                "additionalProperties": true,
-                "description": "One year of the council land-valuation series.",
-                "example": {
-                  "price_per_sqm": 3177.05,
-                  "value": 2270000,
-                  "year": 2025,
-                  "yoy_pct": 0
-                },
-                "properties": {
-                  "price_per_sqm": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Land value per square metre (AUD/sqm). Null when the lot area is unknown.",
-                    "title": "Price Per Sqm"
-                  },
-                  "value": {
-                    "description": "Council land value (AUD).",
-                    "title": "Value",
-                    "type": "number"
-                  },
-                  "year": {
-                    "description": "Valuation year.",
-                    "title": "Year",
-                    "type": "integer"
-                  },
-                  "yoy_pct": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Change vs the previous valued year (%). Null on the first year or after a gap.",
-                    "title": "Yoy Pct"
-                  }
-                },
-                "required": [
-                  "year",
-                  "value"
-                ],
-                "title": "LandValueYear",
-                "type": "object"
-              },
-              "title": "History",
-              "type": "array"
-            },
-            "land_value": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Latest council land value (AUD).",
-              "title": "Land Value"
-            },
-            "zone_desc": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Zoning description (e.g. 'R2 - Low Density Residential').",
-              "title": "Zone Desc"
-            }
-          },
-          "required": [
-            "history"
-          ],
-          "title": "PropertyLandValues",
-          "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[PropertyLandValues]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_PropertyLandValues_"
-}New value: +null

First observedSep 14, 2026

TDQS

A3.7/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 bar is lower, and the description still adds real context beyond them: the coverage boundary (no data for units or non-NSW), the returned field set, and an explicit per-call price of 15¢. It does not explain what an empty result looks like or how coverage gaps in the series are represented.

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?

The purpose and coverage limits are front-loaded in two tight sentences, with the cost note set apart. No filler; the only slight waste is that the field list and the coverage caveat could be ordered to put the exclusion first.

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?

For a one-parameter, no-output-schema tool the description is largely sufficient: it names the returned fields, states the geographic and dwelling-type boundaries, and discloses cost. The remaining gap is the missing explanation of the required gnaf_id, which an agent needs in order to call the tool successfully.

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% and the single parameter gnaf_id is never mentioned in the description, so nothing is added about its format, where to obtain it, or whether an address-based lookup is possible. With one undocumented parameter, the description does not compensate for the schema 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?

States a specific verb+resource (council land valuations for the parcel) and enumerates the returned series (val_2021..val_2025 with YoY change and $/sqm, plus lot area and zoning). The 'for the parcel' phrasing plus the NSW whole-lot-only restriction separates it from suburb-level siblings like suburbs_market_land_values, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit exclusion: held for NSW houses and other whole-lot parcels only, and units or other states return no data. That is strong when-not-to-use guidance, but it does not point the agent at an alternative tool for those excluded cases, so routing is left to inference.

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?