suburbs_market_recent_price_movementThe last four weekly smart-median observations — house price, unit price and house rent — each with its week-on-week percentage change.
| Name | Required | Description | Default |
|---|---|---|---|
| suburb_name | Yes |
Changes observed during successful MCP inspections.
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": "The last 4 weekly smart-median observations, oldest → newest.",
- "example": {
- "area_level": "suburb",
- "area_name": "Belmont North",
- "weeks": [
- {
- "date": "2026-07-19",
- "house_price": 1120000,
- "house_price_change_pct": 0,
- "house_rent": 650,
- "house_rent_change_pct": 0
- },
- {
- "date": "2026-08-09",
- "house_price": 1130000,
- "house_price_change_pct": 0.89,
- "house_rent": 660,
- "house_rent_change_pct": 1.54
- }
- ]
- },
- "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"
- },
- "weeks": {
- "description": "Up to 4 weekly rows, oldest first.",
- "items": {
- "description": "One weekly smart-median observation with week-on-week change.",
- "properties": {
- "date": {
- "description": "ISO date (YYYY-MM-DD) of the weekly observation.",
- "title": "Date",
- "type": "string"
- },
- "house_price": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Median house sale price that week.",
- "title": "House Price"
- },
- "house_price_change_pct": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Change vs the previous week, in percent (e.g. 0.89 = +0.89%).",
- "title": "House Price Change Pct"
- },
- "house_rent": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Median weekly house rent that week.",
- "title": "House Rent"
- },
- "house_rent_change_pct": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Change vs the previous week, in percent.",
- "title": "House Rent Change Pct"
- },
- "unit_price": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Median unit sale price that week.",
- "title": "Unit Price"
- },
- "unit_price_change_pct": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Change vs the previous week, in percent.",
- "title": "Unit Price Change Pct"
- }
- },
- "required": [
- "date"
- ],
- "title": "RecentPriceWeek",
- "type": "object"
- },
- "title": "Weeks",
- "type": "array"
- }
- },
- "required": [
- "area_name",
- "area_level",
- "weeks"
- ],
- "title": "RecentPriceMovement",
- "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[RecentPriceMovement]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_RecentPriceMovement_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds useful behavioral context by specifying the exact data elements (three metrics) and that they include week-on-week changes, which helps the agent anticipate the response shape. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that front-loads the core purpose and immediately lists the included data fields. There is no filler or redundant wording, making it highly efficient for an agent to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, no output schema), the description is nearly complete: it specifies the time window, the metrics included, and the presence of percentage changes. It does not describe the exact output format, but that is not critical for a read-only data retrieval tool. The description adequately equips the agent to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage for the single parameter suburb_name, and the description does not explicitly define it. However, the parameter name and tool name make its meaning obvious, so the agent can infer it accepts a suburb name string. The description does not compensate beyond that, but the triviality of the parameter mitigates the gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns the last four weekly smart-median observations for house price, unit price, and house rent, each with week-on-week percentage change. This distinguishes it from sibling tools like median_rent or price_growth by specifying the exact time window and data components, though it does not explicitly name an alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives such as suburbs_market_median_sale_price_series or suburbs_market_price_growth. It only describes the output, leaving the agent to infer that this is for short-term (4-week) movement, which is not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.