Skip to main content
Glama

DwellDelta - Australian rent check and property indicators

Victorian rents by suburb group

vic_rents
Read-onlyIdempotent

Victoria only: its regions and suburb groups (part of a suburb name works); property_rents also takes one Victorian suburb by whole name. Homes Victoria's Rental Report (CC BY 4.0): the median weekly rent of new leases in the latest quarter, how many leases it rests on, and the change on a year before. The figures are new-lease medians, not advertised rents, and each answer states its quarter, its source line and the source's limits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vic_rents"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoA region, e.g. Inner Melbourne, Geelong, Ballarat
suburb_groupNoA Homes Victoria suburb group, or part of a suburb name

Output Schema

NameRequiredDescriptionDefault
staleYes
adviceYes
limitsNo
cadenceYes
figuresYes
quarterNo
regionsYes
sourcesYes
refusalsYes
publisherYes
data_as_ofNo
all_refusedYes
sample_ruleYes
stale_afterYes
retrieved_atYes
stale_reasonYes
compared_withNo
period_due_byYes
suburb_groupsYes
period_overdueYes
server_versionYes
snapshot_builtNo
snapshot_originYes
period_overdue_reasonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed29 schema fields changed
    • removedOutput schema / definitions / refusal / properties / n_band / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / refusal / properties / reason / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / rent_row / properties / area / anyOf
      Removed value: -[
      -  {
      -    "type": [
      -      "string",
      -      "number"
      -    ]
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / rent_row / properties / change_pct / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / rent_row / properties / council / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / rent_row / properties / first_quartile_aud / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / rent_row / properties / median_weekly_rent_aud / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / rent_row / properties / new_bonds / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / rent_row / properties / new_leases / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / rent_row / properties / region / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / rent_row / properties / small_sample / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / rent_row / properties / suburb_group / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / rent_row / properties / third_quartile_aud / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / rent_row / properties / year_ago_median_aud / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / source / properties / attribution / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / source / properties / feed_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / source / properties / licence / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / source / properties / licence_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / source / properties / licence_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / source / properties / period / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / definitions / source / properties / source / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / compared_with / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / data_as_of / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / figures / items / properties / n_band / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / limits / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / quarter / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / refusals / items / properties / n_band / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / refusals / items / properties / reason / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / snapshot_built / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
  2. First observed

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 the bar is lower, yet the description adds real behavioral context: the data vintage ('latest quarter'), provenance and licence (Homes Victoria Rental Report, CC BY 4.0), the semantic caveat that these are new-lease medians rather than advertised rents, and that every answer carries its quarter, source line and source limitations. It stops short of describing matching behavior when inputs are ambiguous or missing.

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?

Two sentences, front-loaded with the scope constraint ('Victoria only') and the acceptable input forms before the data description. Dense but every clause carries information; the second sentence is long and would read better split, but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and the description still covers vintage, provenance and interpretation limits. The one gap is that both parameters are optional yet the description never says what an argument-free call returns, which an agent needs to know before invoking it.

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 both parameters are already documented with examples, and the description mostly restates them ('part of a suburb name works' mirrors the schema's 'or part of a suburb name'). Its only genuine addition is the cross-tool note that property_rents handles whole-suburb names, which is routing value rather than parameter semantics. Baseline 3 is appropriate.

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 the specific resource (Homes Victoria Rental Report median weekly rents of new leases, latest quarter, lease counts, year-on-year change) and pins the geography to Victoria. It explicitly distinguishes itself from the sibling property_rents, which 'also takes one Victorian suburb by whole name', so an agent can route between them without opening either schema.

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?

It gives clear selection context: Victoria-only scope, region or suburb-group inputs, and partial suburb names are acceptable, while whole-suburb lookups belong to property_rents. It also implicitly steers agents away from advertised-rent tools by stating these are new-lease medians, but it never states what happens when both parameters are omitted or whether they can be combined.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources