Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Leased rents by bedroom, Queensland

suburbs_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": {
      "suburb_name": "<suburb_name>"
    },
    "name": "suburbs_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.
suburb_nameYesSuburb name exactly as /v1/suburbs/list returns it, e.g. `Bondi` or `St Kilda (Vic.)`.

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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely non-structured context: a per-call price of 10¢, the coverage windows, the data currency date, and a pointer to `/v1/datasets/leased-rents-qld` for method and field list. That pricing disclosure is materially useful for an agent deciding whether to call repeatedly.

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 core definition, then coverage, then price — a sensible ordering with little filler. The coverage sentence partially restates the opening sentence's suburb/postcode scope, but overall it is compact for the amount of useful detail conveyed.

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?

For a single-required-parameter read tool with a fully documented schema and no output schema, the description supplies the measures returned, temporal coverage, currency, cost and a docs pointer. The only real gap is that it never states the result granularity/row shape explicitly beyond 'each quarter', though the measures themselves are described.

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 `from`, `to`, `fields` and `suburb_name` including accepted date formats and the full field enumeration. The description only adds the conceptual framing (quarterly granularity, dwelling types, bedroom breakdowns), not new per-parameter syntax or constraints. Baseline 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?

States a specific resource and measures: median weekly rent on new Queensland tenancies plus counts of new bonds, broken down quarterly by dwelling type and bedroom count. The scope (Queensland suburbs from 2017, postcodes from 2012) is concrete. It loses a point because it describes postcode coverage too, which blurs the line against the sibling `postcodes_market_leased_rents_qld` rather than explicitly contrasting with it.

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?

There is no explicit when-to-use / when-not-to-use statement and no named alternative, so the agent must infer selection from the tool name and the coverage windows. The stated date ranges (Sept 2017+ for suburbs, March 2012+ for postcodes) and the currency date do implicitly tell the agent whether a request is in scope. Adequate but leaves routing to inference.

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