Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Geocode · Address search (to GNAF)

geocode_address
Read-onlyIdempotent

Resolve a freeform address string to candidate GNAF identifiers.

Use this before calling any /v1/properties/{gnaf_id}/... route — those endpoints require a GNAF in the path. Returns up to 10 candidates, ranked by Meilisearch score.

Price: 1¢ 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": {
      "address": "<address>"
    },
    "name": "geocode_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesFreeform address string.

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": [
-        {
-          "items": {
-            "additionalProperties": true,
-            "description": "One candidate row returned by the address geocoder.\n\nShape is intentionally open — Meilisearch returns whatever fields\nthe index has indexed (id, name, display_name, property_type, …)\nand we pass them through verbatim so customers can read fields\nthey'd otherwise have to look up separately.",
-            "example": {
-              "abbr": "27 ARLINGTON ST BELMONT NORTH",
-              "display_name": "27 Arlington Street, Belmont North",
-              "id": "GANSW704074813",
-              "name": "27 Arlington Street, Belmont North",
-              "property_type": "house"
-            },
-            "properties": {},
-            "title": "GnafCandidate",
-            "type": "object"
-          },
-          "type": "array"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "The endpoint's payload, or `null` when Microburbs has no value.",
-      "title": "Data"
-    },
-    "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[list[GnafCandidate]]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_list_GnafCandidate__"
-}New value: +null
  2. First observed

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, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: up to 10 candidates ranked by Meilisearch score, and a stated price of 1¢ per call, which matters for an agent deciding how often to call. It does not say what happens on zero matches or how to disambiguate near-ties.

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?

Four short lines, front-loaded with the purpose, then the prerequisite, then the return shape and cost. No sentence is filler and the ordering matches the agent's decision sequence.

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?

With no output schema, the description carries the burden of describing returns and does so adequately (count and ranking basis). Missing detail on the shape of a candidate object and no-match behavior keeps it from full marks for a chained-lookup tool.

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?

Only one parameter, and the schema already documents it at 100% coverage with an example string and minLength. The description's phrase 'freeform address string' restates the schema rather than adding format constraints or parsing rules. Baseline 3 applies.

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 resource ('freeform address string') plus the concrete output ('candidate GNAF identifiers'). The address-level scope distinguishes it from the suburb-level sibling geocode_suburb without needing to open either schema.

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?

Gives an explicit prerequisite chain: call this before any /v1/properties/{gnaf_id}/... route because those require a GNAF in the path. That is strong when-to-use guidance. It stops short of naming geocode_suburb as the alternative for suburb-level lookups, so the sibling routing is only implied.

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