Microburbs Australian Property Data

by au.com.microburbs

Overview Discussions Admin

Property History — rentals

properties_rent_history

Read-onlyIdempotent

Shown in the property report as the 'Property History' card in the Overview section.

All For Rent records, most-recent first.

Price: 30¢ 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_rent_history"
  }
}

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 event in a property's market history — a sale, or a time it was\nadvertised for sale or for rent.\n\nRecords come from listing feeds, so this is the property's *advertised*\nhistory rather than a title/transfer register: a sale that never went to\nmarket may be absent. Records are returned newest first.",
-            "properties": {
-              "address": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "The property's address, title-cased. This is its current address as recorded in the national address file, repeated on every record — not the address text used in that particular listing, so it will not reflect a renumbering or a name change since.",
-                "title": "Address"
-              },
-              "date": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "When the event happened, as `YYYY-MM-DD`. For a `Sold` record this is the sale date; for `For Sale` / `For Rent` it is the date the listing appeared. Note for sold records: where the state land registry is the source this is the contract date rather than settlement, but sold dates sourced from listing portals are not guaranteed to be one or the other — treat it as accurate to the month, not the day.",
-                "title": "Date"
-              },
-              "price": {
-                "anyOf": [
-                  {
-                    "type": "number"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "The money figure attached to the event, in AUD. On `Sold` and `For Sale` records that is the whole price of the property; on `For Rent` it is the advertised rent, normally per week (the Australian convention) — but it is taken from the advertised text as-is and is not converted, so an agent who advertised monthly can leave a monthly figure here. Sanity-check rents that look ~4x too high. Null when the listing showed no number (e.g. 'Auction', 'Contact Agent').",
-                "title": "Price"
-              },
-              "type": {
-                "anyOf": [
-                  {
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Which kind of event this is. One of exactly three values: `'Sold'`, `'For Sale'` (advertised for sale, outcome not necessarily known) or `'For Rent'`. Determines how to read `price` and `date` above.",
-                "title": "Type"
-              }
-            },
-            "title": "HistoryRecord",
-            "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[HistoryRecord]]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_list_HistoryRecord__"
-}New value: +null

First observedSep 14, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds two meaningful behavioral details beyond annotations: ordering is 'most-recent first' and each call costs 30¢, which is operationally important. It still does not describe pagination or output shape, but it does add useful context.

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?

The description is short, front-loaded with the report context, then states the record scope and ordering, and closes with pricing. There is little wasted text. The first sentence is contextual rather than directly operational, but it is still compact and relevant.

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 read-only tool with rich annotations, the description covers record scope, ordering, and cost. However, it leaves the required gnaf_id parameter unexplained and gives no detail about returned fields, which matters because there is no output schema.

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% for the single required parameter, gnaf_id, and the description never mentions it. The phrase 'property report' loosely implies a property identifier, but it does not explain that gnaf_id is the required G-NAF property identifier or what format to use. This leaves the only parameter's meaning to be inferred.

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 it returns 'All For Rent records, most-recent first,' which clearly identifies the resource as rental history records. It implicitly distinguishes from sale history, and the title names rentals. However, it does not explicitly say it is for a property identified by gnaf_id or name the sibling tools like properties_rent_history_latest.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage context is 'Shown in the property report as the Property History card in the Overview section,' which describes report placement rather than when an agent should call this tool. It gives no guidance on when to use it versus properties_rent_history_latest, properties_sale_history, or properties_history_all.

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?