Microburbs Australian Property Data

Property · Geography profile

properties_profile

Read-onlyIdempotent

Resolve a GNAF to its full statistical geography hierarchy (mesh block → SA1 → SA2 → SA3 → SA4 → GCCSA → State) plus the parallel admin chain (LGA, suburb (SAL), postcode). Call this once to get every geography key the rest of the data layers index on.

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": {
      "gnaf_id": "<gnaf_id>"
    },
    "name": "properties_profile"
  }
}

Input Schema

Name	Required	Description	Default
`gnaf_id`	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": [
-        {
-          "description": "Full ABS geo hierarchy for a property — the \"where in ABS world\nis this?\" lookup. Mesh block, SA1–SA4, GCCSA, state, LGA, suburb\n(SAL), postcode. Useful before pulling mesh-block-aggregated layers.",
-          "example": {
-            "gccsa": "Australian Capital Territory",
-            "lga": "Unincorporated ACT",
-            "mesh_block": "80111103200",
-            "postcode": "2902",
-            "sa1": "80101102001",
-            "sa2": "Kambah",
-            "sa3": "Tuggeranong",
-            "sa4": "Australian Capital Territory",
-            "state": "ACT",
-            "suburb": "Kambah (ACT)"
-          },
-          "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 — ABS Suburb and Locality).",
-              "title": "Suburb"
-            }
-          },
-          "required": [
-            "mesh_block",
-            "sa1",
-            "sa2",
-            "sa3",
-            "sa4",
-            "gccsa",
-            "state"
-          ],
-          "title": "PropertyProfile",
-          "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[PropertyProfile]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_PropertyProfile_"
-}New value: +null

First observedSep 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new operational context by quoting a per-call price (3¢) and framing it as a one-shot key lookup, which matters for cost-aware agents. It does not describe the response shape or failure behavior for an unknown GNAF, holding it below 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 sentences, front-loaded with the verb and the full output hierarchy, followed by the cost note. No filler; every clause (output chain, admin chain, one-call rationale, price) earns its place.

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 one-parameter lookup with no output schema, the description adequately conveys what comes back (the geography and admin key chains) and why it is worth calling once. The main gap is the nature and format of a GNAF id, which an unassisted agent may not recognise.

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 description coverage is 0% and the single parameter is undocumented in the schema, so the description carries the burden. "Resolve a GNAF" tells the agent the input is a GNAF identifier, but gives no format, example, or validity constraints. It partially compensates but leaves the caller guessing.

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?

States a specific verb ("Resolve") and a specific resource (a GNAF to its statistical geography hierarchy), then enumerates the exact output chain (mesh block → SA1 → SA2 → SA3 → SA4 → GCCSA → State) plus the admin chain (LGA, SAL, postcode). This is clearly distinguishable from geocode_address and the properties_* / suburbs_* siblings, which take other inputs and return other subjects.

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

Usage Guidelines4/5

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

"Call this once to get every geography key the rest of the data layers index on" gives strong when-to-use guidance and implies it is the upstream/prerequisite call for many siblings. It stops short of explicitly naming alternatives or stating when not to call it (e.g. when you already hold the SA2 keys).

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?