Microburbs Australian Property Data

by au.com.microburbs

Overview Discussions Admin

Suburb · Finder scope regions

suburbs_finder_regions

Read-onlyIdempotent

SA4 regions grouped by state — the values accepted by states / regions on search. 0c.

Free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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": [
-        {
-          "description": "Scope options — SA4 regions grouped by state abbreviation.",
-          "example": {
-            "regions": {
-              "NSW": [
-                "Sydney - City and Inner South",
-                "Newcastle and Lake Macquarie"
-              ]
-            }
-          },
-          "properties": {
-            "regions": {
-              "additionalProperties": {
-                "items": {
-                  "type": "string"
-                },
-                "type": "array"
-              },
-              "description": "`{state: [sa4, ...]}` — pass a state to `states` and/or an SA4 to `regions`.",
-              "title": "Regions",
-              "type": "object"
-            }
-          },
-          "required": [
-            "regions"
-          ],
-          "title": "RegionsResponse",
-          "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[RegionsResponse]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_RegionsResponse_"
-}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 absent destructive effects. The description adds the insight that it's free and provides regional groupings, but it does not elaborate on output format or limitations (e.g., completeness of state coverage).

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 exceptionally brief and to the point, covering the core purpose and a key benefit (free) in two sentences. No wasted words or redundancy.

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?

Given zero parameters and no output schema, the description is complete for basic use. However, it lacks details on the structure or granularity of the returned region data (e.g., count, naming conventions), which could be important for an agent planning to use it as a lookup.

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

Parameters4/5

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

With zero parametersached to the tool, there are no schema fields to document. The description's focus on 'values accepted by states/regions' clarifies how the output can be used as input elsewhere, adding value for a no-parameter tool.

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 clearly states the tool provides SA4 regions grouped by state, serving as accepted values for `states`/`regions` on search. It distinguishes itself from broader finder tools by specifying it scopes regions, though it doesn't explicitly name a sibling alternative.

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?

The description implies usage as a reference for filtering search queries, but it doesn't explicitly state when to use it versus alternatives like suburbs_finder_search or area_stats_regions. No clear context on prerequisites or selection criteria is provided.

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?