Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

LGA · Leased rents by bedroom, Victorian councils

lga_market_leased_rents_vic
Read-onlyIdempotent

Median weekly rent on new Victorian tenancies, and the number of new bonds, each quarter since 1999 by dwelling type and bedrooms (flats and houses), for every Victorian council area.

Coverage: All 79 Victorian council areas with at least 5 new bonds in the quarter and group; June quarter 1999 onwards. Current to 2026-06-30. Full description, field list and method: /v1/datasets/leased-rents-vic.

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": {
      "lga_name": "<lga_name>"
    },
    "name": "lga_market_leased_rents_vic"
  }
}

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, bonds_all, bonds_flat_1bed, bonds_flat_2bed, bonds_flat_3bed, bonds_house_2bed, bonds_house_3bed, bonds_house_4bed. Omit for all.
lga_nameYesCouncil (LGA) name exactly as /v1/lga/list returns it, e.g. `Lake Macquarie`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the read-only, idempotent, closed-world safety profile, and the description adds substantive behavior beyond them: a 10¢ per-call price, the suppression rule (areas need at least 5 new bonds in the quarter and group, so gaps are meaningful rather than errors), and an explicit currency cutoff. That is exactly the kind of cost and data-availability context an agent needs before calling.

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?

Well front-loaded: the dataset headline comes first, then coverage, then price, then a docs pointer, with no wasted prose. The bolded price line and the doc reference both earn their place, though the block is slightly longer than strictly necessary for a four-parameter read tool.

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 read-only statistical dataset with no output schema, the description supplies the essentials: granularity, time span, coverage thresholds, currency and cost. Return shape and pagination are not described, but they are delegated to the referenced dataset documentation rather than left silent.

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, an explicit field list and the lga_name lookup rule all documented in the schema itself. The description adds no parameter-level detail beyond naming dwelling type and bedroom breakdown, so it sits at the baseline for a fully documented schema.

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 description names a precise dataset: median weekly rent on new Victorian tenancies plus new bond counts, quarterly since 1999, broken down by dwelling type and bedrooms, for every Victorian council area. The explicit geographic granularity (council area, not postcode or suburb) and jurisdiction (Victoria) distinguish it from the NSW/Qld leased-rents siblings without needing to name them.

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?

Useful context is given: minimum-5-bonds coverage, June quarter 1999 onwards, current to 2026-06-30, and a pointer to the full dataset page. It does not, however, explicitly route the agent away from related tools (e.g. suburb- or postcode-level rent series) or state when a different granularity should be preferred.

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