properties_surroundings_listing_history_signalsLatest sold/rent dates and likely-owner-status signal per nearby property.
Price: 20¢ per call.
| Name | Required | Description | Default |
|---|---|---|---|
| gnaf_id | 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": "Listing-history owner-status signals for properties around the subject.",
- "example": {
- "count": 97,
- "gnaf_pid": "GANSW704360755",
- "radius_m": 200,
- "recent_window_years": 10,
- "signals": [
- {
- "gnaf_pid": "GANSW704349559",
- "last_sold_date": "2021-11-23",
- "last_sold_years_ago": 4.6,
- "signal": "previously_for_sale"
- },
- {
- "gnaf_pid": "GANSW704341221",
- "last_sold_date": "2015-01-27",
- "last_sold_years_ago": 11.4,
- "signal": "no_recent_listings"
- }
- ],
- "summary": {
- "no_recent_listings": 24,
- "previously_for_sale": 55,
- "previously_rented": 18
- }
- },
- "properties": {
- "count": {
- "description": "Properties with any listing history (never-listed properties carry no signal and are omitted).",
- "title": "Count",
- "type": "integer"
- },
- "gnaf_pid": {
- "description": "The subject property's GNAF PID.",
- "title": "Gnaf Pid",
- "type": "string"
- },
- "radius_m": {
- "description": "Radius of the search box around the subject, metres.",
- "title": "Radius M",
- "type": "integer"
- },
- "recent_window_years": {
- "description": "Recency window used to derive the signals (years).",
- "title": "Recent Window Years",
- "type": "integer"
- },
- "signals": {
- "description": "Per-property signals, sorted by GNAF PID.",
- "items": {
- "additionalProperties": true,
- "description": "Derived owner-status signal for one nearby property.",
- "properties": {
- "gnaf_pid": {
- "description": "GNAF PID of the property.",
- "title": "Gnaf Pid",
- "type": "string"
- },
- "last_rent_date": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Most recent rental listing date (YYYY-MM-DD).",
- "title": "Last Rent Date"
- },
- "last_rent_years_ago": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Years since the last rental listing (1 dp).",
- "title": "Last Rent Years Ago"
- },
- "last_sold_date": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Most recent Sold/Buy listing date (YYYY-MM-DD).",
- "title": "Last Sold Date"
- },
- "last_sold_years_ago": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Years since the last sale listing (1 dp).",
- "title": "Last Sold Years Ago"
- },
- "signal": {
- "description": "Likely owner status: recent rent listing → `previously_rented` (likely investor); recent sale → `previously_for_sale` (likely mortgaged); neither within the window → `no_recent_listings` (likely owned outright).",
- "enum": [
- "previously_rented",
- "previously_for_sale",
- "no_recent_listings"
- ],
- "title": "Signal",
- "type": "string"
- }
- },
- "required": [
- "gnaf_pid",
- "signal"
- ],
- "title": "ListingHistorySignal",
- "type": "object"
- },
- "title": "Signals",
- "type": "array"
- },
- "summary": {
- "additionalProperties": true,
- "description": "Signal counts across the returned properties.",
- "properties": {
- "no_recent_listings": {
- "description": "Properties with no listing inside the window.",
- "title": "No Recent Listings",
- "type": "integer"
- },
- "previously_for_sale": {
- "description": "Properties with a recent sale.",
- "title": "Previously For Sale",
- "type": "integer"
- },
- "previously_rented": {
- "description": "Properties with a recent rental.",
- "title": "Previously Rented",
- "type": "integer"
- }
- },
- "required": [
- "previously_rented",
- "previously_for_sale",
- "no_recent_listings"
- ],
- "title": "ListingSignalSummary",
- "type": "object"
- }
- },
- "required": [
- "gnaf_pid",
- "radius_m",
- "recent_window_years",
- "count",
- "signals",
- "summary"
- ],
- "title": "SurroundingListingSignals",
- "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[SurroundingListingSignals]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_SurroundingListingSignals_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the per-property granularity and the price, but it does not disclose behavior for missing data, invalid gnaf_id values, or how the 'likely-owner-status' signal is expressed.
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 two short sentences: the first front-loads the core output, and the second gives the price. Both sentences earn their place, with no filler or repetition of annotation details.
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?
For a single-parameter read tool with no output schema, the description provides enough intent-level clarity to attempt a call, but it leaves out the response structure, interpretation of the owner-status signal, and the radius context beyond the title. Additional detail about the 200 m scope or expected output shape would make it complete.
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 input schema provides only a required gnaf_id string with no description, and the description never mentions gnaf_id or explains how to obtain it. With 0% schema description coverage, the tool description should compensate for the parameter semantics, and it does not.
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 states the output content: latest sold/rent dates and likely-owner-status signal per nearby property. This is clear enough to infer the operation, though it lacks an explicit verb like 'returns' or 'lists' and does not differentiate itself from overlapping sibling tools such as properties_neighbours or properties_surroundings_properties.
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?
No guidance is provided about when to use this tool versus alternatives. There are many nearby property-related sibling tools, but the description only explains what the tool returns and its price, never when it should be preferred or avoided.
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.