Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Easements

suburbs_shapes_easements
Read-onlyIdempotent

Shown in the suburb report as the 'Easements' map layer (explorer) in the Risks section.

Registered easement geometries intersecting the suburb (GeoJSON FeatureCollection).

Price: 15¢ 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": {
      "suburb_name": "<suburb_name>"
    },
    "name": "suburbs_shapes_easements"
  }
}

Input Schema

NameRequiredDescriptionDefault
geojsonNoWhen false, geometry is dropped — every Feature keeps its `properties` but its `geometry` is null. Use it to fetch the counts and per-feature attributes without the coordinates (default true — response unchanged).
suburb_nameYes

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": "Registered easement geometries intersecting the suburb.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "count": 8,
-            "geojson": {
-              "features": [
-                {
-                  "geometry": {
-                    "coordinates": [
-                      [
-                        [
-                          151.66,
-                          -32.99
-                        ],
-                        [
-                          151.67,
-                          -32.99
-                        ],
-                        [
-                          151.67,
-                          -33
-                        ],
-                        [
-                          151.66,
-                          -32.99
-                        ]
-                      ]
-                    ],
-                    "type": "Polygon"
-                  },
-                  "properties": {
-                    "category": "drainage"
-                  },
-                  "type": "Feature"
-                }
-              ],
-              "type": "FeatureCollection"
-            }
-          },
-          "properties": {
-            "area_level": {
-              "const": "suburb",
-              "description": "Always 'suburb'.",
-              "title": "Area Level",
-              "type": "string"
-            },
-            "area_name": {
-              "description": "Canonical ABS SAL name.",
-              "title": "Area Name",
-              "type": "string"
-            },
-            "count": {
-              "description": "Number of easement features returned.",
-              "title": "Count",
-              "type": "integer"
-            },
-            "geojson": {
-              "additionalProperties": true,
-              "description": "GeoJSON FeatureCollection — easement geometries intersecting the suburb. Properties: `category`, `name`. Geometry is null on every Feature when the request passes `?geojson=false`.",
-              "title": "Geojson",
-              "type": "object"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "count",
-            "geojson"
-          ],
-          "title": "SuburbEasements",
-          "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[SuburbEasements]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SuburbEasements_"
-}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 read-only, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds two things annotations do not: the spatial-intersection filter semantics (features crossing the suburb boundary, not contained within it) and a per-call price of 15¢, which is meaningful cost guidance. It falls short of disclosing what an empty result looks like.

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 lines: dataset identity first, then return type, then cost. No redundant restatement of the name, and the cost callout earns its place. Slightly fragmented prose, but nothing wasted.

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 correctly states the return type (GeoJSON FeatureCollection) but does not describe the per-feature properties an agent would need to parse results or the behavior when no easements intersect. Combined with the undocumented suburb_name parameter, this leaves real gaps for a paid, two-parameter tool.

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 coverage is only 50%: the geojson toggle is fully documented in the schema, but suburb_name has no documentation anywhere. The description does not explain whether suburb_name takes a name, an ABS code, or a canonical form, nor whether it is matched exactly or fuzzily, so it fails to compensate for the coverage 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 names a specific verb and resource (returns registered easement geometries) with a clear scope (intersecting the suburb, as GeoJSON FeatureCollection). The reference to the 'Easements' map layer in the Risks section further pins down what dataset this is, distinguishing it implicitly from sibling layers like hazards or busy roads, though no sibling is named 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 report-layer reference ('shown in the suburb report as the Easements map layer'), which tells an agent this is the easement-layer equivalent but not when to prefer it over other risk layers. There is no statement of prerequisites, such as which suburb identifier format to supply or where to obtain it.

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