Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

List SA4s

sa4_list
Read-onlyIdempotent

All Australian SA4s. Optional ?state= filter. Returns {sa4, state} per row. Flat cost.

Price: 1¢ per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sa4_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoFilter by state / territory. Optional — ~110 SA4s nationally.

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": {
-            "description": "One row in the SA4 directory.",
-            "example": {
-              "sa4": "Newcastle and Lake Macquarie",
-              "state": "NSW"
-            },
-            "properties": {
-              "sa4": {
-                "description": "SA4 name.",
-                "title": "Sa4",
-                "type": "string"
-              },
-              "state": {
-                "description": "State / Territory abbreviation (NSW, VIC, ...).",
-                "title": "State",
-                "type": "string"
-              }
-            },
-            "required": [
-              "sa4",
-              "state"
-            ],
-            "title": "Sa4ListItem",
-            "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[Sa4ListItem]]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_list_Sa4ListItem__"
-}New value: +null
  2. First observed

TDQS

A3.6/5.0
Behavior3/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 real value by stating the return shape `{sa4, state}` per row (no output schema exists) and the flat-cost billing model. It does not mention pagination or ordering, which would matter for a ~110-row listing.

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 fragments, front-loaded with the resource scope, then filter, return shape, and cost. No wasted wording.

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?

For a single-optional-param list tool with no output schema, the description covers scope, filter, return fields and cost. Only pagination/ordering behavior is unstated, a minor gap given the small result set.

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?

Schema coverage is 100% and the `state` parameter is already documented as an optional state/territory filter with the national count. The description only restates it as `?state=`, adding a minor query-syntax hint rather than new meaning; baseline 3 applies.

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 (list) and resource (all Australian SA4s), which is immediately clear. It does not explicitly contrast with the sibling sa4_profile, though the list/profile naming distinction is reasonably self-evident.

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?

It notes the state filter is optional and that ~110 SA4s exist nationally via schema, implying usage for enumeration. However, it gives no explicit guidance on when to use this versus sa4_profile or how to then drill into a specific SA4.

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