Suburb · Sale-price growth forecast
suburbs_forecast_saleRead-onlyIdempotent
1-year sale-price growth forecast (low / most-likely / high).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| suburb_name | Yes |
Microburbs Australian Property Data
Schema Changelog
Changes observed during successful MCP inspections.
Changed1 schema field changed
- changed
Output 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": "12-month sale-price growth forecast by property type.", - "example": { - "area_level": "suburb", - "area_name": "Belmont North", - "house": { - "confidence": 2, - "high": 0.0927, - "low": 0.0379, - "most_likely": 0.0686 - }, - "metric": "sale_price_growth_forecast", - "unit": { - "confidence": 2, - "high": 0.0993, - "low": 0.0353, - "most_likely": 0.0762 - } - }, - "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" - }, - "house": { - "anyOf": [ - { - "description": "A forecast expressed as a range rather than a single number — a\nmost-likely outcome with a plausible low and high either side.\n\nEverywhere this shape appears the three figures are **growth over the\nnext 12 months, as a decimal fraction**: 0.0379 means +3.79% over the\nyear, and a negative value means a fall. Multiply by 100 to display as a\npercentage. Present the band, not just `most_likely` — the width between\n`low` and `high` is the honest part of the forecast.", - "properties": { - "confidence": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ], - "description": "How much weight to put on the forecast, on a 0–5 scale where 5 is most confident — it is not a percentage or a probability. High confidence means the low-to-high band is tight and the underlying market has enough sales to model; low confidence usually means a thin, volatile market where the band is wide.", - "title": "Confidence" - }, - "high": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ], - "description": "Optimistic end of the 12-month growth forecast, same decimal-fraction scale as `low`. Not a ceiling.", - "title": "High" - }, - "low": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ], - "description": "Pessimistic end of the 12-month growth forecast, as a decimal fraction (0.0379 = +3.79%; negatives are falls). Not a floor — outcomes can land below it.", - "title": "Low" - }, - "most_likely": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ], - "description": "Central estimate of 12-month growth, as a decimal fraction. The single number to quote if you can only show one, but it should carry `low`/`high` with it.", - "title": "Most Likely" - } - }, - "title": "ForecastBand", - "type": "object" - }, - { - "type": "null" - } - ], - "description": "House forecast band." - }, - "metric": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Metric label, e.g. 'sale_price_growth_forecast'.", - "title": "Metric" - }, - "unit": { - "anyOf": [ - { - "description": "A forecast expressed as a range rather than a single number — a\nmost-likely outcome with a plausible low and high either side.\n\nEverywhere this shape appears the three figures are **growth over the\nnext 12 months, as a decimal fraction**: 0.0379 means +3.79% over the\nyear, and a negative value means a fall. Multiply by 100 to display as a\npercentage. Present the band, not just `most_likely` — the width between\n`low` and `high` is the honest part of the forecast.", - "properties": { - "confidence": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ], - "description": "How much weight to put on the forecast, on a 0–5 scale where 5 is most confident — it is not a percentage or a probability. High confidence means the low-to-high band is tight and the underlying market has enough sales to model; low confidence usually means a thin, volatile market where the band is wide.", - "title": "Confidence" - }, - "high": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ], - "description": "Optimistic end of the 12-month growth forecast, same decimal-fraction scale as `low`. Not a ceiling.", - "title": "High" - }, - "low": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ], - "description": "Pessimistic end of the 12-month growth forecast, as a decimal fraction (0.0379 = +3.79%; negatives are falls). Not a floor — outcomes can land below it.", - "title": "Low" - }, - "most_likely": { - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ], - "description": "Central estimate of 12-month growth, as a decimal fraction. The single number to quote if you can only show one, but it should carry `low`/`high` with it.", - "title": "Most Likely" - } - }, - "title": "ForecastBand", - "type": "object" - }, - { - "type": "null" - } - ], - "description": "Unit forecast band." - } - }, - "required": [ - "area_name", - "area_level" - ], - "title": "ForecastSale", - "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[ForecastSale]", - "type": "object", - "x-fastmcp-top-level-schema": "ApiResponse_ForecastSale_" -}New value: +null
- First observed
TDQS
B3.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, idempotent, and non-destructive behavior, so the description's main added value is clarifying the forecast scenario outputs (low / most-likely / high). There is no contradiction with annotations, but no additional behavioral context such as data limitations, availability, or confidence interpretation is disclosed.
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?
The description is a single, succinct sentence that front-loads the core meaning and includes the key output scenarios. Every part of the sentence adds relevant information with no waste.
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 simple read-only, single-parameter tool, the description covers the core purpose and expected output structure. It does not describe the response values in detail, but with no output schema, the low/most-likely/high breakdown provides reasonable completeness for an agent to understand what the tool returns.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage and the description does not explain the suburb_name parameter beyond the tool's title. While the parameter name is somewhat self-explanatory, the description does not clarify acceptable formats, name variations, or how the forecast applies to the provided suburb.
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 clearly identifies the resource: a 1-year sale-price growth forecast for a suburb, and specifies the three scenario outputs: low / most-likely / high. It is specific enough to distinguish this from many siblings, though it lacks an explicit verb and does not directly differentiate itself from nearby tools like suburbs_market_price_growth or suburbs_hero_price_growth_12mo.
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?
No guidance is provided about when to use this tool versus alternative suburb market or growth tools. The description states only what the tool returns, not the conditions for choosing it over siblings such as suburbs_market_price_growth or suburbs_street_forecasts.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.