Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Council Rates

suburbs_development_council_rates
Read-onlyIdempotent

Shown in the suburb report as the 'Council Rates' card in the Development section.

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

Price: 5¢ 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_development_council_rates"
  }
}

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": "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
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds genuinely useful context beyond them: the per-call price of 5¢ and that the value is an LGA-level aggregate rather than a suburb-level one. It omits any note on data coverage, currency/units, or behavior when a suburb has no matching LGA.

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 padding, and the actual metric definition is stated plainly. The report-placement sentence is mildly secondary and leads before the metric, which is slightly backwards for an agent deciding whether to call it, 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?

For a one-parameter read tool with no output schema, the description conveys the returned quantity and its aggregation level, which is close to sufficient. It still leaves the agent guessing about currency/units, null handling for unmatched suburbs, and input format for suburb_name.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter suburb_name is undocumented, so the description must compensate. It does partially: 'for the suburb's LGA' clarifies that the returned figure is the LGA aggregate for the given suburb, which is a real semantic addition. It says nothing about accepted input format (name string vs. ID) or how ambiguous suburb names are resolved.

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 metric: the average annual residential council rate for the suburb's LGA, plus where it surfaces in the report ('Council Rates' card, Development section). That is far more specific than the name alone, though it never names or distinguishes itself from the many sibling suburbs_development_* metrics.

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?

There is no when-to-use guidance and no mention of alternatives among the development siblings (e.g. council_intelligence, development_profile). The only usage signal is the implied 'call this when you want council rates', which the name already conveys.

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