Microburbs Australian Property Data

Leased rents by bedroom, NSW postcodes

postcodes_market_leased_rents_nsw

Read-onlyIdempotent

Median weekly rent actually signed on new NSW tenancies, and the number of new bonds, each quarter since 2021 by dwelling type and bedrooms (flats, houses, townhouses), for every NSW postcode.

Coverage: NSW (and ACT-range postcodes lodged with NSW) postcodes with at least 5 new bonds in the quarter and group; March quarter 2021 onwards. Current to 2026-09-30. Full description, field list and method: /v1/datasets/leased-rents-nsw.

Price: 10¢ 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": {
      "postcode": "<postcode>"
    },
    "name": "postcodes_market_leased_rents_nsw"
  }
}

Input Schema

Name	Required	Description
`to`	No	Last period to include, same formats as `from`.
`from`	No	First period to include: 2020, 2020-Q3, 2020-07 or 2020-07-01.
`fields`	No	Comma-separated subset of: rent_all, rent_flat_1bed, rent_flat_2bed, rent_flat_3bed, rent_house_2bed, rent_house_3bed, rent_house_4bed, rent_townhouse_2bed, rent_townhouse_3bed, bonds_all, bonds_flat_1bed, bonds_flat_2bed, bonds_flat_3bed, bonds_house_2bed, bonds_house_3bed, bonds_house_4bed, bonds_townhouse_2bed, bonds_townhouse_3bed. Omit for all.
`postcode`	Yes	Four-digit postcode, e.g. `2026`.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 13, 2026

TDQS

A4.1/5.0

Behavior4/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 safety is covered. The description adds genuinely non-obvious behavior: a 10¢ per-call charge, a data-recency boundary (current to 2026-09-30), and a suppression rule (groups with fewer than 5 new bonds are excluded). It does not cover auth, rate limits, or response shape.

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 metric definition is front-loaded in one dense sentence, followed by short, scannable Coverage and Price callouts and a doc pointer. Every element earns its place, though the opening sentence is long enough to be split for readability.

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?

With no output schema, the description still conveys units (median weekly rent, bond counts), temporal coverage, and the geographic scope, and it points to /v1/datasets/leased-rents-nsw for the field list and method. It does not describe the record shape (one row per quarter per group) or any pagination/volume limits, which is the remaining gap for a data-returning tool.

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 100%, with from/to formats, the full valid field list, and a postcode example all documented inline. The description adds no additional parameter meaning — it only restates the available breakdowns, which the `fields` enum already enumerates — so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names the exact metrics (median weekly rent signed on new tenancies, count of new bonds), the unit of observation (NSW postcode), the time granularity (quarterly since 2021), and the breakdown (dwelling type and bedroom count). The 'nsw' in the name and the NSW/ACT-range coverage note cleanly separate it from the sibling qld and vic leased-rents tools.

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

Usage Guidelines4/5

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

The Coverage line tells the agent the exact conditions under which data exists — postcodes with at least 5 new bonds in the quarter and group, March quarter 2021 onward — which prevents futile queries against thin or out-of-range postcodes. It does not explicitly say when to reach for a sibling (e.g. qld/vic equivalents) or when not to use this tool, so it stops short of a full routing statement.

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?