Skip to main content
Glama

Microburbs Australian Property Data

Supply Pressure (by suburb)

suburbs_market_supply_pressure
Read-onlyIdempotent

Shown in the suburb report as the 'Supply Pressure' map layer (full-screen map explorer) in the Market section.

For-sale listings per 100 dwellings over the 90 days of our supply snapshot (point-in-time, not refreshed daily) — per mesh block + suburb rollup.

Price: 20¢ 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_supply_pressure"
  }
}

Input Schema

NameRequiredDescriptionDefault
suburb_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "available": {
      -      "anyOf": [
      -        {
      -          "type": "boolean"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "description": "`false` on no-data responses. Omitted on success — branch on `data !== null` if you want a single discriminator.",
      -      "title": "Available"
      -    },
      -    "data": {
      -      "anyOf": [
      -        {
      -          "additionalProperties": true,
      -          "description": "Per-mesh-block supply pressure + suburb rollup.",
      -          "example": {
      -            "area_level": "suburb",
      -            "area_name": "Belmont North",
      -            "dwellings": 3980,
      -            "listings_90d": 42,
      -            "listings_per_100_dwellings": 1.06,
      -            "mbs": [
      -              {
      -                "dwellings": 54,
      -                "listings_90d": 0,
      -                "listings_per_100_dwellings": 0,
      -                "mb": "11205845900"
      -              }
      -            ]
      -          },
      -          "properties": {
      -            "area_level": {
      -              "description": "Always 'suburb' for these endpoints.",
      -              "title": "Area Level",
      -              "type": "string"
      -            },
      -            "area_name": {
      -              "description": "Suburb (SAL) name.",
      -              "title": "Area Name",
      -              "type": "string"
      -            },
      -            "dwellings": {
      -              "anyOf": [
      -                {
      -                  "type": "integer"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ],
      -              "description": "Total dwelling stock across the suburb's MBs.",
      -              "title": "Dwellings"
      -            },
      -            "listings_90d": {
      -              "anyOf": [
      -                {
      -                  "type": "integer"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ],
      -              "description": "Total 90-day listings across the suburb's MBs.",
      -              "title": "Listings 90D"
      -            },
      -            "listings_per_100_dwellings": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ],
      -              "description": "Suburb rollup: listings per 100 dwellings, last 90 days.",
      -              "title": "Listings Per 100 Dwellings"
      -            },
      -            "mbs": {
      -              "description": "Per-mesh-block breakdown.",
      -              "items": {
      -                "description": "Supply pressure for one mesh block.",
      -                "properties": {
      -                  "dwellings": {
      -                    "anyOf": [
      -                      {
      -                        "type": "integer"
      -                      },
      -                      {
      -                        "type": "null"
      -                      }
      -                    ],
      -                    "description": "Dwelling stock in the MB.",
      -                    "title": "Dwellings"
      -                  },
      -                  "listings_90d": {
      -                    "anyOf": [
      -                      {
      -                        "type": "integer"
      -                      },
      -                      {
      -                        "type": "null"
      -                      }
      -                    ],
      -                    "description": "Raw 90-day listings count.",
      -                    "title": "Listings 90D"
      -                  },
      -                  "listings_per_100_dwellings": {
      -                    "anyOf": [
      -                      {
      -                        "type": "number"
      -                      },
      -                      {
      -                        "type": "null"
      -                      }
      -                    ],
      -                    "description": "For-sale listings per 100 dwellings, last 90 days.",
      -                    "title": "Listings Per 100 Dwellings"
      -                  },
      -                  "mb": {
      -                    "description": "ABS mesh-block code (MB_CODE21).",
      -                    "title": "Mb",
      -                    "type": "string"
      -                  }
      -                },
      -                "required": [
      -                  "mb"
      -                ],
      -                "title": "SupplyPressureMb",
      -                "type": "object"
      -              },
      -              "title": "Mbs",
      -              "type": "array"
      -            }
      -          },
      -          "required": [
      -            "area_name",
      -            "area_level",
      -            "mbs"
      -          ],
      -          "title": "SupplyPressure",
      -          "type": "object"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "description": "The endpoint's payload, or `null` when Microburbs has no value."
      -    },
      -    "message": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "description": "Human-readable explanation. Omitted on success.",
      -      "title": "Message"
      -    },
      -    "reason": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "description": "Machine-readable slug naming the no-data condition (e.g. `no_avm_for_GANSW704074813`). Stable per endpoint. Omitted on success.",
      -      "title": "Reason"
      -    }
      -  },
      -  "title": "ApiResponse[SupplyPressure]",
      -  "type": "object",
      -  "x-fastmcp-top-level-schema": "ApiResponse_SupplyPressure_"
      -}New value: +null
  2. First observed

TDQS

B3.3/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 closed-world scope, so the safety profile is covered. The description does add genuinely new behavioral context: the data is a point-in-time snapshot not refreshed daily, and each call costs 20¢. That cost and freshness disclosure is valuable, but return shape and per-call limits are unstated.

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

Conciseness5/5

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

Three short lines, each earning its place: location in the product, the metric definition, and the cost. The defining sentence is front-loaded and there is no padding or repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only metric this is close to sufficient, with the metric formula, snapshot cadence, and price all disclosed. What remains missing is how suburb_name should be formatted and, absent an output schema, any indication of the return payload or mesh-block vs suburb result structure.

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 coverage is 0% for the single suburb_name parameter, so the description must carry the load. It indicates the record is resolved at suburb level via the 'suburb rollup' phrasing, but gives no format, matching, or disambiguation guidance for naming a suburb, leaving a real gap for the one required input.

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 names the specific metric ('for-sale listings per 100 dwellings over the 90 days') and its granularity ('per mesh block + suburb rollup'), which is far more than a restatement of the title. It does not, however, contrast itself with adjacent siblings such as suburbs_market_months_of_supply, so the agent must infer the distinction from the metric wording alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage framing is that it appears as a map layer in the suburb report's Market section, which is UI context rather than invocation guidance. There is no statement of when to prefer this metric over months-of-supply or other supply metrics, and no prerequisites or exclusions.

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