Skip to main content
Glama

DwellDelta - Australian rent check and property indicators

What DwellDelta covers

data_sources
Read-onlyIdempotent

The sources behind DwellDelta's figures, their licences, and what it cannot answer (what any one home sold for, the rent of a single street or home, new-bond rents by area outside NSW, VIC, QLD, WA, SA, TAS and New Zealand, sale prices by area outside NSW, listings, advice).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
rulesNo
staleYes
adviceYes
cadenceYes
sourcesYes
publisherYes
data_as_ofNo
stale_afterYes
retrieved_atYes
stale_reasonYes
cannot_answerNo
period_due_byYes
period_overdueYes
server_versionYes
snapshot_builtNo
snapshot_originYes
period_overdue_reasonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 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 / cannot_answer / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / data_as_of / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / rules / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
    • removedOutput schema / properties / snapshot_built / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {}
      -]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds value by disclosing the payload's nature — provenance, licences, and explicit non-coverage — which tells the agent this is a reference/enumeration response rather than data. It omits whether the content is static documentation or live-queried, which would have earned a higher score against an already well-annotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence that leads with the positive coverage before the exclusions, which is the right order. The parenthetical grows unwieldy, though, enumerating six states plus New Zealand for one exclusion and stacking eight unrelated gap categories, which makes it harder to scan than a short structured list would be.

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?

With zero parameters, an output schema present and full annotation coverage, the remaining burden is telling the agent what domain the tool spans — and the positive clause plus the coverage-gap list does that thoroughly. The only gap is the absence of a cue about how to act on the result, such as redirecting the agent to a sibling when it hits an exclusion.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description does not introduce any phantom parameters or argument-like language.

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 states a specific resource: the data sources behind DwellDelta's figures, their licences, and the coverage gaps. The negative list (single-home sold prices, single-street rents, listings, advice) makes the tool's remit concrete and distinguishes it from the measurement siblings. It falls short of 5 because it never names a sibling tool directly, leaving the agent to infer which one handles the excluded cases.

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?

The 'what it cannot answer' list effectively communicates when this tool will not help, which is genuine when-not-to-use guidance. However, it never states the positive trigger (e.g., 'call this first to check whether a query is answerable') and names no alternatives among area_rents, property_rents, rent_check or the state sale-price tools. Usage is implied rather than directed.

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