Microburbs Australian Property Data

by au.com.microburbs

Overview Discussions Admin

Property · Meet the neighbours

properties_neighbours

Read-onlyIdempotent

Shown in the property report as the 'Meet the neighbours' map in the Overview section.

Adjoining-parcel neighbours, enriched with address + property type + bed/bath/garage from the latest matching listing.

Price: 30¢ 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_neighbours"
  }
}

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": [
-        {
-          "example": {
-            "neighbours": [
-              {
-                "address": "3 TAMAR STREET",
-                "gnaf_pid": "GANSW704083204",
-                "property_type": "house"
-              },
-              {
-                "address": "16 HARRISON STREET",
-                "gnaf_pid": "GANSW704073018",
-                "property_type": "house"
-              },
-              {
-                "address": "14 HARRISON STREET",
-                "gnaf_pid": "GANSW704073016",
-                "property_type": "house"
-              }
-            ]
-          },
-          "properties": {
-            "neighbours": {
-              "description": "Adjoining cadastral parcels, with address + attributes when available.",
-              "items": {
-                "additionalProperties": true,
-                "description": "One neighbouring property (adjoining cadastral parcel).",
-                "properties": {
-                  "address": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Full address from the GNAF feed.",
-                    "title": "Address"
-                  },
-                  "bathrooms": {
-                    "anyOf": [
-                      {
-                        "type": "integer"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Bathroom count from the most recent listing, if any.",
-                    "title": "Bathrooms"
-                  },
-                  "bedrooms": {
-                    "anyOf": [
-                      {
-                        "type": "integer"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Bedroom count from the most recent listing, if any.",
-                    "title": "Bedrooms"
-                  },
-                  "garage_spaces": {
-                    "anyOf": [
-                      {
-                        "type": "integer"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Garage spaces from the most recent listing, if any.",
-                    "title": "Garage Spaces"
-                  },
-                  "gnaf_pid": {
-                    "description": "GNAF persistent identifier.",
-                    "title": "Gnaf Pid",
-                    "type": "string"
-                  },
-                  "property_type": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Property type (house, unit, townhouse, ...). Lowercase.",
-                    "title": "Property Type"
-                  }
-                },
-                "required": [
-                  "gnaf_pid"
-                ],
-                "title": "Neighbour",
-                "type": "object"
-              },
-              "title": "Neighbours",
-              "type": "array"
-            }
-          },
-          "required": [
-            "neighbours"
-          ],
-          "title": "Neighbours",
-          "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[Neighbours]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_Neighbours_"
-}New value: +null

First observedSep 14, 2026

TDQS

B3/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 openWorldHint=false, so the safety profile is covered without the description's help. The description adds genuinely new context: a per-call price (30¢) and the data provenance ('latest matching listing'), which implies enrichment fields may be missing or stale when no listing matches. It does not say what happens when a parcel has no matching listing, nor how many neighbours are returned.

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?

Two short blocks, front-loaded with what the tool returns and back-loaded with the cost warning, so nothing important is buried. The UI-placement sentence is somewhat ornamental but earns a little context. No filler or repetition.

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?

With no output schema, the description partially covers the return shape by naming the enrichment fields, and it discloses cost — both helpful. It still leaves the required identifier unexplained and says nothing about result volume, ordering, or failure modes, which matters for a per-call paid tool with one undocumented required parameter.

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% and the description never mentions gnaf_id at all — no format, no source (e.g. from geocode_address or properties_profile), no indication of whether it is a G-NAF PID or address string. With a single required parameter and zero schema documentation, the description was the only place to compensate and does not.

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 resource (adjoining-parcel neighbours for a property) and even enumerates the enrichment fields (address, property type, bed/bath/garage from the latest matching listing). This is far from tautological and lets an agent understand the payload without opening a schema. It stops short of naming how it differs from the many similarly named siblings (properties_surroundings_parcels, properties_surroundings_properties, suburbs_shapes_neighbours).

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 only usage signal is the UI placement ('shown in the property report as the Meet the neighbours map'), which implies report context but gives no when-to-use or when-not-to-use guidance. Nothing tells the agent whether to prefer this over properties_surroundings_parcels or the suburb-level neighbours tools. Given ~90 siblings with overlapping 'nearby/neighbours' semantics, this is a real omission.

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?