Microburbs Australian Property Data

Property · Zoning

properties_development_zoning_code

Read-onlyIdempotent

Shown in the property report as the 'Zoning' card in the Development section.

Primary zoning at the property's point: the human-readable zone name and broader category, plus the statutory code (R2, B4, ...) where we hold it (NSW; null elsewhere).

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_development_zoning_code"
  }
}

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": {
-            "category": "Residential Zones",
-            "code": "R2",
-            "name": "Low Density Residential"
-          },
-          "properties": {
-            "category": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Broader category bucket, e.g. 'Residential Zones', 'Business Zones'.",
-              "title": "Category"
-            },
-            "code": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Parenthesised code (e.g. 'R2', 'B4', 'IN1') when the council's feed includes one. Many regional NSW + Adelaide + QLD councils don't — in which case this is null and the human-readable label is on `name`.",
-              "title": "Code"
-            },
-            "name": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Human-readable zone class, e.g. 'Low Density Residential'.",
-              "title": "Name"
-            }
-          },
-          "title": "ZoningCode",
-          "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[ZoningCode]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_ZoningCode_"
-}New value: +null

First observedSep 14, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, closed-world and non-destructive behavior, so the description does not need to. It adds real value beyond them: per-call pricing (3¢) and the important coverage caveat that the statutory code is only present for NSW and null elsewhere. It does not describe pagination or response shape, but that is minor for a single-record lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The bolded price line and the field enumeration are well front-loaded and earn their place. The opening sentence about which report card it renders in is UI context of limited value to an agent and could be cut without loss.

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 lookup with no output schema, the description does well to enumerate the returned fields and the NSW-only caveat. The unresolved gap is the identifier itself: an agent cannot tell what a valid gnaf_id looks like or where to obtain one.

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?

Only one parameter, gnaf_id, and the schema coverage is 0%, so the description carries the full burden of explaining it — yet the identifier is never described. The mention of 'the property's point' faintly implies a property identifier is required but gives no format, source, or constraint for gnaf_id.

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?

States the exact resource and scope: 'Primary zoning at the property's point' returning zone name, category, and statutory code. This is specific and readable against the sibling zoning_overlays tool, though the description never names that sibling to draw the contrast 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?

The phrase 'Primary zoning at the property's point' implicitly scopes it away from overlays or suburb-level lookups, and 'where we hold it (NSW; null elsewhere)' signals a data limitation. However, there is no explicit when-to-use/when-not guidance or named alternative, leaving routing to inference.

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?