Skip to main content
Glama

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Recent sales (last 3 years)

suburbs_sales_recent
Read-onlyIdempotent

Properties sold in the suburb over the last 3 years, with beds/baths/land size, sale price and date, and coordinates.

Paginated: total reports how many sales are available for the suburb (counted before limit/offset), so you can page through the full feed. Flat price per call regardless of page size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoSales to return (default 20, max 200).
offsetNoRow offset — page through the feed with `limit`.
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": "Properties sold in the suburb over the last 3 years, paginated.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "results": [
-              {
-                "address": "9 Kanundra Street",
-                "bathrooms": 3,
-                "bedrooms": 2,
-                "gnaf_pid": "GANSW704074941",
-                "lat": -33.02135461,
-                "lng": 151.66919805,
-                "property_type": "House",
-                "sold_date": "2026-03-30",
-                "sold_price": 1005000
-              },
-              {
-                "address": "9 Hope Street",
-                "bathrooms": 1,
-                "bedrooms": 3,
-                "gnaf_pid": "GANSW704073843",
-                "land_size": 844,
-                "lat": -33.01951863,
-                "lng": 151.67430967,
-                "property_type": "House",
-                "sold_date": "2026-03-27",
-                "sold_price": 910000
-              }
-            ]
-          },
-          "properties": {
-            "area_level": {
-              "description": "Always 'suburb' for these endpoints.",
-              "title": "Area Level",
-              "type": "string"
-            },
-            "area_name": {
-              "description": "Suburb (SAL) name.",
-              "title": "Area Name",
-              "type": "string"
-            },
-            "results": {
-              "description": "Sold properties, most significant first. Capped by `limit`.",
-              "items": {
-                "additionalProperties": true,
-                "description": "One sold property.",
-                "properties": {
-                  "address": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Street address (title-cased).",
-                    "title": "Address"
-                  },
-                  "bathrooms": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Bathroom count.",
-                    "title": "Bathrooms"
-                  },
-                  "bedrooms": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Bedroom count.",
-                    "title": "Bedrooms"
-                  },
-                  "gnaf_pid": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "GNAF property ID.",
-                    "title": "Gnaf Pid"
-                  },
-                  "land_size": {
-                    "anyOf": [
-                      {
-                        "type": "integer"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Land size in m², where known.",
-                    "title": "Land Size"
-                  },
-                  "lat": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Latitude (WGS84).",
-                    "title": "Lat"
-                  },
-                  "lng": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Longitude (WGS84).",
-                    "title": "Lng"
-                  },
-                  "property_type": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Bucketed type: House / Townhouse / Unit / Land / Other.",
-                    "title": "Property Type"
-                  },
-                  "sold_date": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Sale date (YYYY-MM-DD).",
-                    "title": "Sold Date"
-                  },
-                  "sold_price": {
-                    "anyOf": [
-                      {
-                        "type": "number"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ],
-                    "description": "Sale price (AUD).",
-                    "title": "Sold Price"
-                  }
-                },
-                "title": "RecentSaleRow",
-                "type": "object"
-              },
-              "title": "Results",
-              "type": "array"
-            },
-            "total": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Sales available for this suburb — counted before `limit`/`offset`, so it stays accurate while paging.",
-              "title": "Total"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "results"
-          ],
-          "title": "RecentSales",
-          "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[RecentSales]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_RecentSales_"
-}New value: +null
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds genuine value beyond that by disclosing pagination semantics (total counted before limit/offset so the full feed can be paged) and pricing behavior (flat price per call). These are behavioral traits not derivable from the annotations or schema, making the description informative for the agent.

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?

Two short paragraphs with the core purpose front-loaded in the first sentence, followed by a tightly scoped pagination note. Every sentence earns its place — the field list defines the return shape, and the pagination paragraph conveys total semantics and pricing without verbosity. No wasted or redundant sentences.

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?

Despite lacking an output schema, the description compensates by enumerating the return fields (beds/baths/land size, sale price, date, coordinates) and explaining pagination behavior with total semantics. For a read-only feed tool whose safety profile is covered by annotations, this is reasonably complete — the only gap is that suburb_name is not described, but it is obvious from the tool's purpose. Nothing critical is missing for correct invocation.

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 description coverage is 67%, with limit and offset already documented in the input schema. The description reinforces pagination concepts (total, limit/offset) but adds little new meaning about the parameters themselves. The undocumented required parameter suburb_name is not elaborated in the description, though its meaning is self-evident from the tool's purpose. The description adds marginal value over the schema rather than compensating 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 states a specific verb and resource: properties sold in the suburb over the last 3 years, and enumerates the returned fields (beds/baths/land size, sale price, date, coordinates). It is clearly a sales feed tool, distinct from suburbs_sales_summary (aggregate statistics) by the nature of the content, though it never names any sibling to explicitly disambiguate. Purpose is clear but sibling differentiation is implicit rather than stated.

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 description explains operational behavior — pagination mechanics and flat pricing — but offers no guidance on when to choose this tool over siblings such as suburbs_sales_summary or properties_sale_history. The context is clear (it is the individual-sales feed for a suburb) but there are no explicit when/when-not conditions or named alternatives. The usage context is implied rather than directed.

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