Microburbs Australian Property Data

Suburb · Average council rates

suburbs_development_council_rates

Read-onlyIdempotent

Average annual residential council rate for the suburb's LGA.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`suburb_name`	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": "Average annual residential council rate for the suburb's LGA.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "avg_rate_aud_yr": 1584,
-            "data_source": "NSW_OLG_AVG",
-            "lga": "Lake Macquarie"
-          },
-          "properties": {
-            "area_level": {
-              "description": "Always 'suburb'.",
-              "title": "Area Level",
-              "type": "string"
-            },
-            "area_name": {
-              "description": "Suburb (SAL) name.",
-              "title": "Area Name",
-              "type": "string"
-            },
-            "avg_rate_aud_yr": {
-              "description": "Average annual residential rate (AUD per year).",
-              "title": "Avg Rate Aud Yr",
-              "type": "integer"
-            },
-            "data_source": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Provenance of the rate figure (e.g. 'NSW_OLG_AVG').",
-              "title": "Data Source"
-            },
-            "lga": {
-              "description": "Local government area the suburb belongs to.",
-              "title": "Lga",
-              "type": "string"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "lga",
-            "avg_rate_aud_yr"
-          ],
-          "title": "SuburbCouncilRates",
-          "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[SuburbCouncilRates]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SuburbCouncilRates_"
-}New value: +null

First observedSep 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no behavioral context beyond its core function—no mention of data freshness, aggregation method, or potential quirks. It is consistent with annotations but does not enhance transparency beyond what structured data already provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, compact sentence with no redundancy. It states the core function clearly and front-loads the metric. Every word earns its place.

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?

For a simple tool with one parameter and no output schema, the description is minimally adequate. It tells the agent what the tool returns (average rate) and the input (suburb). However, it omits details like currency, units, or how the LGA is derived from the suburb, which could be inferred but are not stated. Given the low complexity, this is borderline acceptable but not fully complete.

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 description does not mention the parameter at all. While the single parameter 'suburb_name' is self-explanatory from its name and the tool's context, the description does not clarify expected format, validity constraints, or whether it should be a full name or an abbreviation. With low schema coverage, the description should compensate but fails to do so.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific metric (average annual residential council rate) for a specific resource (the suburb's LGA). It is distinct from the many sibling tools, which focus on different metrics like median prices, crime, or demographics. The verb 'average' and the resource 'council rate' make the purpose unambiguous.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives. With over 100 siblings, many of which also return suburb-level data, an agent receives no routing cues. The description implies usage but does not explicitly state when it is appropriate or when another tool (e.g., suburbs_market_strata_levies) would be better.

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?