Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Mesh Block · Mesh-block profile (by mb_code)

mbs_profile
Read-onlyIdempotent

The mesh block's upward geography chain — SA1, SA2/3/4, GCCSA, state — plus the parallel admin chain (LGA, suburb (SAL), postcode).

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": {
      "mb_code": "<mb_code>"
    },
    "name": "mbs_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
mb_codeYes

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": [
-        {
-          "description": "Upward ABS chain for a mesh block, plus admin attributes.",
-          "example": {
-            "gccsa": "Rest of NSW",
-            "lga": "Lake Macquarie",
-            "mesh_block": "10434270000",
-            "postcode": "2280",
-            "sa1": "11101120618",
-            "sa2": "Belmont - Bennetts Green",
-            "sa3": "Lake Macquarie - East",
-            "sa4": "Newcastle and Lake Macquarie",
-            "state": "NSW",
-            "suburb": "Belmont North"
-          },
-          "properties": {
-            "gccsa": {
-              "description": "Greater Capital City Statistical Area.",
-              "title": "Gccsa",
-              "type": "string"
-            },
-            "lga": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Local Government Area.",
-              "title": "Lga"
-            },
-            "mesh_block": {
-              "description": "ABS Mesh Block code.",
-              "title": "Mesh Block",
-              "type": "string"
-            },
-            "postcode": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Postcode (POA).",
-              "title": "Postcode"
-            },
-            "sa1": {
-              "description": "SA1 code.",
-              "title": "Sa1",
-              "type": "string"
-            },
-            "sa2": {
-              "description": "SA2 name.",
-              "title": "Sa2",
-              "type": "string"
-            },
-            "sa3": {
-              "description": "SA3 name.",
-              "title": "Sa3",
-              "type": "string"
-            },
-            "sa4": {
-              "description": "SA4 name.",
-              "title": "Sa4",
-              "type": "string"
-            },
-            "state": {
-              "description": "State / Territory.",
-              "title": "State",
-              "type": "string"
-            },
-            "suburb": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Suburb (SAL).",
-              "title": "Suburb"
-            }
-          },
-          "required": [
-            "mesh_block",
-            "sa1",
-            "sa2",
-            "sa3",
-            "sa4",
-            "gccsa",
-            "state"
-          ],
-          "title": "MeshBlockProfile",
-          "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[MeshBlockProfile]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_MeshBlockProfile_"
-}New value: +null
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new information beyond that: the per-call price (3¢), which matters for call planning, and an explicit inventory of the returned geography levels. It does not say what happens with an invalid or unknown mb_code, which keeps it from a 5.

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?

Two short, front-loaded sentences: the return payload first, the cost second. No filler, no restatement of the title. Nothing could be cut without losing information.

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 read-only, single-parameter lookup with full annotations and no output schema, the description covers what the tool returns and its cost, which is most of what an agent needs. The remaining gap is practical: how to obtain or format a valid mb_code before calling.

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% for the single required parameter, so the description carries the full burden and adds almost nothing about mb_code — no format, length, or example. It only implies the parameter identifies a mesh block via the title. A note like '11-digit ASGS mesh block code' would have closed the 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?

The description concretely enumerates what a 'profile' returns: the upward ASGS chain (SA1, SA2/3/4, GCCSA, state) plus the admin chain (LGA, SAL, postcode). Combined with the title's 'by mb_code', an agent can tell this is a single-mesh-block geography resolver. It stops at 4 because it never distinguishes itself from adjacent profile tools (lga_profile, sa4_profile, suburbs_profile) that take different key types.

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 or when-not-to-use guidance, and no statement of prerequisites such as 'requires a valid mb_code; use mbs_list to find one'. The agent must infer that this is the mesh-block analogue of the other *_profile tools. Only the title's 'by mb_code' hints at context.

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