Skip to main content
Glama

DwellDelta - Australian rent check and property indicators

Australian property market indicators

market_indicators
Read-onlyIdempotent

Latest Australian property market indicators - RBA cash rate, unemployment, wage growth, rents by capital city, new housing lending, lending standards and arrears, dwelling approvals and completions - each with its period, source, licence and limits. Some figures are the publisher's own and some are calculated by DwellDelta from the publisher's figures; none is a forecast. geography, if given, narrows the answer to the figures for one place.

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": "market_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
geographyNoNSW, Australia, or a capital city

Output Schema

NameRequiredDescriptionDefault
staleYes
adviceYes
cadenceYes
sourcesYes
publisherYes
data_as_ofNo
indicatorsYes
sample_sizeYes
stale_afterYes
retrieved_atYes
stale_reasonYes
period_due_byYes
period_overdueYes
server_versionYes
snapshot_builtNo
snapshot_originYes
sample_size_noteYes
period_overdue_reasonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changed
    • 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 / data_as_of / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / indicators / items / properties / attribution / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / indicators / items / properties / change / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": {},
      -    "properties": {
      -      "over": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {}
      -        ]
      -      },
      -      "unit": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {}
      -        ]
      -      },
      -      "value": {
      -        "anyOf": [
      -          {
      -            "type": "number"
      -          },
      -          {}
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / indicators / items / properties / geography / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / indicators / items / properties / id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / indicators / items / properties / licence / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / indicators / items / properties / limit / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / indicators / items / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / indicators / items / properties / period / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / indicators / items / properties / source / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / indicators / items / properties / unit / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / indicators / items / properties / value / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / snapshot_built / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses provenance that matters: each figure carries period, source, licence and limits, and some values are the publisher's own while others are DwellDelta calculations from publisher data. It also rules out forecasts, which prevents misuse. It does not discuss freshness/lag or return structure, but the output schema covers the latter.

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 resource and its contents, then provenance caveats, then the geography qualifier. The indicator list is long but each item is a genuine payload component, and there is no filler beyond a somewhat dense single-sentence construction.

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 zero-required-parameter read tool with a full output schema and complete annotation coverage, the description supplies what the structured fields do not: content inventory, provenance/calculation provenance, no-forecast caveat, and geography scoping. Only the absence of explicit sibling routing keeps it from full marks.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so baseline is 3; the description adds real meaning by stating that geography is optional and that omitting it returns figures across places rather than for 'one place'. That optionality/aggregation behavior is not spelled out in the schema itself.

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?

Names the resource precisely and enumerates its contents (RBA cash rate, unemployment, wage growth, rents by capital city, lending, arrears, approvals, completions), so an agent knows exactly what it returns. It does not explicitly distinguish itself from siblings like property_rents or area_rents, which also touch rent data, leaving the boundary to be inferred.

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 implied by content rather than stated: the tool is for 'latest' indicator snapshots and the geography clause tells you how to narrow scope. There is no explicit when-to-use or when-not guidance versus the rent-specific or sale-price siblings, so an agent must infer the split.

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