Microburbs Australian Property Data

by au.com.microburbs

Overview Discussions Admin

Property · Recent sales

properties_comparables_recent_sales_nearby

Read-onlyIdempotent

Shown in the property report as the 'Recent sales' table tab in the Properties section.

Recent comparable sales in a small radius around the subject parcel.

Price: 4¢ 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_comparables_recent_sales_nearby"
  }
}

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": [
-        {
-          "items": {
-            "additionalProperties": true,
-            "description": "One recent sale within the subject property's CMA search radius.",
-            "example": {
-              "address": "30 Arlington Street, Belmont North",
-              "bath_count": 2,
-              "bed_count": 3,
-              "distance_m": 65,
-              "dwelling_type": "house",
-              "sale_date": "2024-08-12",
-              "sale_price": 815000
-            },
-            "properties": {
-              "address": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Street address.",
-                "title": "Address"
-              },
-              "bath_count": {
-                "anyOf": [
-                  {
-                    "type": "integer"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Bathrooms.",
-                "title": "Bath Count"
-              },
-              "bed_count": {
-                "anyOf": [
-                  {
-                    "type": "integer"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Bedrooms.",
-                "title": "Bed Count"
-              },
-              "distance_m": {
-                "anyOf": [
-                  {
-                    "type": "integer"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Distance from the subject property in metres.",
-                "title": "Distance M"
-              },
-              "dwelling_type": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "house / unit / townhouse / ...",
-                "title": "Dwelling Type"
-              },
-              "sale_date": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "ISO date (YYYY-MM-DD).",
-                "title": "Sale Date"
-              },
-              "sale_price": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Sale price, AUD.",
-                "title": "Sale Price"
-              }
-            },
-            "title": "RecentSale",
-            "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[RecentSale]]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_list_RecentSale__"
-}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 the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add operational context it doesn't already have. It does so with a concrete cost disclosure ('4¢ per call') and a scope qualifier ('small radius'), both of which matter for an agent deciding whether to call it. It stops short of describing result size or what 'comparable' means.

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 sentences, front-loaded with the report placement and then the actual definition, with the cost bolded for visibility. The parenthetical UI framing ('Properties section', 'table tab') is slightly extraneous but not wasteful enough to penalize further.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 1-param tool with no output schema and no annotation-independent detail, the description leaves the only parameter wholly unexplained and gives no sense of what a 'recent sale' record contains or how many are returned. An agent could not construct a valid, purposeful call from this alone without guessing at gnaf_id.

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 description coverage is 0% and the single parameter 'gnaf_id' is undocumented in the schema. The description never explains that it is a property identifier, where to obtain one (e.g. via geocode_address), or any format expectations, 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 states a specific verb+resource ('Recent comparable sales') with an explicit spatial scope ('in a small radius around the subject parcel'). That distinguishes it reasonably well from portfolio-wide siblings like properties_comparables_all, though it never names those alternatives directly.

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-placement sentence ('Shown in the property report as the "Recent sales" table tab'), which signals the report context but gives no when/when-not guidance. There is no routing advice versus properties_comparables_all, properties_comparables_cma_comp_set, or suburbs_sales_recent.

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?