Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Property · Meet the neighbours — parcels (200 m)

properties_surroundings_parcels
Read-onlyIdempotent

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

Cadastral parcel polygons (GeoJSON) for properties around the subject.

Price: 25¢ 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_surroundings_parcels"
  }
}

Input Schema

NameRequiredDescriptionDefault
gnaf_idYes

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": [
-        {
-          "additionalProperties": true,
-          "description": "Cadastral parcel polygons for every property around the subject.",
-          "example": {
-            "count": 127,
-            "gnaf_pid": "GANSW704360755",
-            "parcels": {
-              "features": [
-                {
-                  "geometry": {
-                    "coordinates": [
-                      [
-                        [
-                          [
-                            151.221417,
-                            -33.800987
-                          ],
-                          [
-                            151.221318,
-                            -33.801078
-                          ],
-                          [
-                            151.221308,
-                            -33.801256
-                          ],
-                          [
-                            151.221417,
-                            -33.800987
-                          ]
-                        ]
-                      ]
-                    ],
-                    "type": "MultiPolygon"
-                  },
-                  "properties": {
-                    "gnaf_pid": "GANSW704355807",
-                    "is_subject": false
-                  },
-                  "type": "Feature"
-                }
-              ],
-              "type": "FeatureCollection"
-            },
-            "radius_m": 200
-          },
-          "properties": {
-            "count": {
-              "description": "Number of parcel features returned.",
-              "title": "Count",
-              "type": "integer"
-            },
-            "gnaf_pid": {
-              "description": "The subject property's GNAF PID.",
-              "title": "Gnaf Pid",
-              "type": "string"
-            },
-            "parcels": {
-              "additionalProperties": true,
-              "description": "GeoJSON FeatureCollection, one feature per parcel.",
-              "properties": {
-                "features": {
-                  "description": "One feature per parcel.",
-                  "items": {
-                    "additionalProperties": true,
-                    "description": "One cadastral parcel as a GeoJSON Feature.",
-                    "properties": {
-                      "geometry": {
-                        "additionalProperties": true,
-                        "description": "Parcel polygon, 6 dp coords.",
-                        "properties": {
-                          "coordinates": {
-                            "description": "Nested coordinate arrays per the GeoJSON spec, lon first.",
-                            "title": "Coordinates"
-                          },
-                          "type": {
-                            "description": "GeoJSON geometry type, e.g. 'MultiPolygon'.",
-                            "title": "Type",
-                            "type": "string"
-                          }
-                        },
-                        "required": [
-                          "type",
-                          "coordinates"
-                        ],
-                        "title": "GeoJsonGeometry",
-                        "type": "object"
-                      },
-                      "properties": {
-                        "additionalProperties": true,
-                        "description": "Feature properties: `gnaf_pid` and `is_subject`.",
-                        "title": "Properties",
-                        "type": "object"
-                      },
-                      "type": {
-                        "const": "Feature",
-                        "description": "Always 'Feature'.",
-                        "title": "Type",
-                        "type": "string"
-                      }
-                    },
-                    "required": [
-                      "type",
-                      "properties",
-                      "geometry"
-                    ],
-                    "title": "ParcelFeature",
-                    "type": "object"
-                  },
-                  "title": "Features",
-                  "type": "array"
-                },
-                "type": {
-                  "const": "FeatureCollection",
-                  "description": "Always 'FeatureCollection'.",
-                  "title": "Type",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "type",
-                "features"
-              ],
-              "title": "ParcelFeatureCollection",
-              "type": "object"
-            },
-            "radius_m": {
-              "description": "Radius of the search box around the subject, metres.",
-              "title": "Radius M",
-              "type": "integer"
-            }
-          },
-          "required": [
-            "gnaf_pid",
-            "radius_m",
-            "count",
-            "parcels"
-          ],
-          "title": "SurroundingParcels",
-          "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[SurroundingParcels]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SurroundingParcels_"
-}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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add operational context, and it does: it discloses the return payload type (GeoJSON) and a per-call price of 25¢, which is genuinely decision-relevant. It stops short of describing polygon volume or geometry precision.

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?

Three short, front-loadable statements with no padding; the price note is set off clearly. The opening report-location sentence is somewhat redundant with the title but still orients the reader quickly.

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?

For a simple one-parameter read, the description covers output format (GeoJSON) and cost, which is the main missing piece given no output schema. It remains thin on the identifier contract and on how the 200 m extent relates to the returned parcels.

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?

The single parameter gnaf_id has 0% schema description coverage, and the description adds no clarification of what identifier it expects, its format, or whether it must belong to the subject property. With one undocumented parameter and no output schema, the description should 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 and output shape: 'Cadastral parcel polygons (GeoJSON) for properties around the subject,' with the 200 m radius supplied by the title. That is enough to separate it from record-returning siblings such as properties_surroundings_properties, though it never names those siblings explicitly.

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?

Usage is only implied through the map/report framing ('Meet the neighbours' map in the Overview section), which tells an agent this is a mapping/context layer rather than a data lookup. There is no explicit when-to-use, when-not-to-use, or pointer to the alternative parcel/property-neighbour tools.

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