Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Postcode · Leased rents by bedroom, Queensland

postcodes_market_leased_rents_qld
Read-onlyIdempotent

Median weekly rent on new Queensland tenancies, and the number of new bonds, each quarter by dwelling type and bedrooms (flats, houses, townhouses), for Queensland suburbs (from 2017) and postcodes (from 2012).

Coverage: Queensland suburbs (September quarter 2017 onwards) and postcodes (March quarter 2012 onwards) with any published value. Current to 2026-09-30. Full description, field list and method: /v1/datasets/leased-rents-qld.

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_qld"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast period to include, same formats as `from`.
fromNoFirst period to include: 2020, 2020-Q3, 2020-07 or 2020-07-01.
fieldsNoComma-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.
postcodeYesFour-digit postcode, e.g. `2026`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With readOnlyHint/idempotentHint/openWorldHint already covering safety, the description adds genuinely non-structured context: the per-call price (10¢), data currency date, and a pointer to the full method/field documentation. It does not describe pagination, row limits, or what a sparse-coverage postcode returns, which are the remaining behavioral unknowns.

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?

Front-loaded with the measure and grain, then coverage, then price — a sensible order with no filler sentences. The coverage sentence is dense but each clause carries information the agent needs (spatial unit, start dates, currency).

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?

No output schema exists, and the description does compensate by naming the two returnable measure families and their quarterly/bedroom breakdown, plus a doc pointer for the field list. The main gap is the suburb-vs-postcode ambiguity in a postcode-required tool, which could make an agent unsure whether the results are restricted to the supplied postcode.

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%, so the schema already documents postcode, from, to and fields with formats and a full field enumeration. The description only echoes the fields at a high level ('by dwelling type and bedrooms') and adds no format, default, or validation semantics beyond the schema, so the baseline of 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 the specific measures (median weekly rent on new tenancies and count of new bonds) and the grain (quarterly, by dwelling type and bedrooms), so the agent knows exactly what resource is returned. It is weakened by mixing dataset-level scope ('Queensland suburbs ... and postcodes') into a tool that is clearly postcode-scoped, and it never distinguishes itself from the sibling suburbs_market_leased_rents_qld.

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: the coverage paragraph tells the agent the valid spatial and temporal window (postcodes from March quarter 2012, current to 2026-09-30), which implicitly says when a call will return data. There is no explicit 'use this when…' or 'use the suburbs variant instead when…' 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 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