Microburbs Australian Property Data

List mesh blocks (by suburb)

mbs_list

Read-onlyIdempotent

Mesh-block codes inside a suburb. sal is required for now — nationwide / by-LGA / by-SA3 listings will land later when there's a story for the large payloads (a single LGA can hit a few thousand mesh blocks).

Price: 3¢ 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": {
      "sal": "<sal>"
    },
    "name": "mbs_list"
  }
}

Input Schema

Name	Required	Description	Default
`sal`	Yes	Required. Suburb (SAL) to list mesh blocks for.

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": [
-        {
-          "items": {
-            "description": "One row in the MB directory — code + the suburb / state it\nsits in (so the customer can read it back without a profile\nround-trip).",
-            "example": {
-              "mb_code": "10434270000",
-              "state": "NSW",
-              "suburb": "Belmont North"
-            },
-            "properties": {
-              "mb_code": {
-                "description": "ABS Mesh Block code.",
-                "title": "Mb Code",
-                "type": "string"
-              },
-              "state": {
-                "description": "State / Territory abbreviation.",
-                "title": "State",
-                "type": "string"
-              },
-              "suburb": {
-                "description": "Suburb (SAL) the MB sits in.",
-                "title": "Suburb",
-                "type": "string"
-              }
-            },
-            "required": [
-              "mb_code",
-              "suburb",
-              "state"
-            ],
-            "title": "MeshBlockListItem",
-            "type": "object"
-          },
-          "type": "array"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "The endpoint's payload, or `null` when Microburbs has no value.",
-      "title": "Data"
-    },
-    "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[list[MeshBlockListItem]]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_list_MeshBlockListItem__"
-}New value: +null

First observedSep 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: a 3¢ per-call price, the fact that only the suburb scope currently works, and a warning that unscoped variants would return payloads in the thousands. That cost and payload context is exactly the kind of thing annotations cannot express.

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 core statement and the required-parameter constraint are front-loaded, and the pricing note is short and scannable. The middle clause about future nationwide/LGA/SA3 listings is somewhat speculative filler, but it does justify why the API is currently restricted, so it mostly earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, read-only list tool with rich annotations and no output schema, the description covers what is returned (mesh-block codes), how scope is constrained, and a non-obvious cost warning. Nothing an agent needs in order to call this correctly is missing.

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?

With one parameter at 100% schema description coverage, the schema already explains that 'sal' is the required suburb (SAL). The description repeats that it is required and adds no format, code-list, or casing guidance beyond the schema, so it meets the baseline without extending it.

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 states a specific verb and resource — listing mesh-block codes scoped to a suburb — and the title reinforces the suburb scoping. It is clear what the tool returns, but it never names or distinguishes itself from nearby siblings such as mbs_profile, suburbs_shapes_mesh_blocks, or properties_context_mesh_blocks, so an agent must infer the split.

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 description explains the current scope constraint (suburb only, other geographies 'later') and why the scope is limited (large payloads for an LGA). That is useful context but it is about the tool's roadmap, not about when to pick this over an alternative that also returns mesh-block information. No explicit when-not or alternative-naming guidance is given.

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?