AVnester — Indian Real Estate Intelligence

Compare Indian localities head-to-head

compare_localities

Read-onlyIdempotent

Compare 2–3 localities in one city side-by-side: price trends, livability, investment grade, strengths, and watchouts. Use when the user asks "X vs Y" or "which is better for buying/renting" about neighborhoods. Covers cities AVnester publishes locality guides for; others return supported=false — surface the scopeMessage. For specific LISTINGS by ID, use compare_properties instead.

Input Schema

Name	Required	Description
`city`	Yes	Indian city covering all compared localities.
`localities`	Yes	2–3 localities to compare (array, not comma-separated string).
`propertyType`	No	Property type for comparison.

Output Schema

Name	Required	Description	Default
`city`	Yes
`cards`	Yes
`supported`	Yes
`comparison`	Yes
`disclaimer`	Yes
`handoffUrl`	Yes
`localities`	Yes
`attribution`	Yes
`scopeMessage`	No
`supportedCities`	No
`resolvedLocalities`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

addedOutput schema / properties / resolvedLocalities

Added value: +{
+  "additionalProperties": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "type": "object"
+}

Changed4 schema fields changedOct 1, 2026
- changedOutput schema / properties / comparison / additionalProperties / properties / confidence / enum
```
Previous value: -[
-  "high",
-  "medium",
-  "low"
-]New value: +[
+  "high",
+  "medium",
+  "low",
+  null
+]
```
- changedOutput schema / properties / comparison / additionalProperties / properties / livabilityScoreBasis / enum
```
Previous value: -[
-  "editorial-estimate"
-]New value: +[
+  "editorial-estimate",
+  null
+]
```
- addedOutput schema / properties / comparison / additionalProperties / properties / priceTrends / items / properties / estimated
```
Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / comparison / additionalProperties / properties / priceTrends / items / properties / pricePerSqftInr
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```

Changed8 schema fields changedSep 23, 2026

addedOutput schema / properties / comparison / additionalProperties / properties / asOfMonth
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

addedOutput schema / properties / comparison / additionalProperties / properties / confidence

Added value: +{
+  "enum": [
+    "high",
+    "medium",
+    "low"
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / comparison / additionalProperties / properties / priceGrowth1YPct
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / comparison / additionalProperties / properties / pricePerSqftInr
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / comparison / additionalProperties / properties / rent2bhkInr
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / comparison / additionalProperties / properties / rentalYieldPct
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / comparison / additionalProperties / properties / sourceCount
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```

changedOutput schema / properties / comparison / additionalProperties / required

Previous value: -[
-  "priceTrends",
-  "livabilityScore",
-  "livabilityScoreBasis",
-  "investmentGrade",
-  "strengthTags",
-  "watchouts",
-  "highlights"
-]New value: +[
+  "priceTrends",
+  "pricePerSqftInr",
+  "rent2bhkInr",
+  "rentalYieldPct",
+  "priceGrowth1YPct",
+  "asOfMonth",
+  "sourceCount",
+  "confidence",
+  "livabilityScore",
+  "livabilityScoreBasis",
+  "investmentGrade",
+  "strengthTags",
+  "watchouts",
+  "highlights"
+]

Changed2 schema fields changedJun 22, 2026

addedOutput schema / properties / comparison / additionalProperties / properties / livabilityScoreBasis

Added value: +{
+  "enum": [
+    "editorial-estimate"
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / comparison / additionalProperties / required

Previous value: -[
-  "priceTrends",
-  "livabilityScore",
-  "investmentGrade",
-  "strengthTags",
-  "watchouts",
-  "highlights"
-]New value: +[
+  "priceTrends",
+  "livabilityScore",
+  "livabilityScoreBasis",
+  "investmentGrade",
+  "strengthTags",
+  "watchouts",
+  "highlights"
+]

Changed2 schema fields changedJun 13, 2026

addedOutput schema / properties / cards

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "data": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "priority": {
+        "type": "integer"
+      },
+      "template": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "template",
+      "data",
+      "priority"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "city",
-  "localities",
-  "supported",
-  "comparison",
-  "attribution",
-  "handoffUrl",
-  "disclaimer"
-]New value: +[
+  "city",
+  "localities",
+  "supported",
+  "comparison",
+  "attribution",
+  "handoffUrl",
+  "disclaimer",
+  "cards"
+]

Changed1 schema field changedJun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "attribution": {
+      "enum": [
+        "AVnester"
+      ]
+    },
+    "city": {
+      "type": "string"
+    },
+    "comparison": {
+      "additionalProperties": {
+        "additionalProperties": true,
+        "properties": {
+          "highlights": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "investmentGrade": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "livabilityScore": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "priceTrends": {
+            "items": {
+              "additionalProperties": true,
+              "properties": {
+                "avgPriceInr": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "period": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "period",
+                "avgPriceInr"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "strengthTags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "watchouts": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "priceTrends",
+          "livabilityScore",
+          "investmentGrade",
+          "strengthTags",
+          "watchouts",
+          "highlights"
+        ],
+        "type": "object"
+      },
+      "type": "object"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "handoffUrl": {
+      "format": "uri",
+      "type": "string"
+    },
+    "localities": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "scopeMessage": {
+      "type": "string"
+    },
+    "supported": {
+      "type": "boolean"
+    },
+    "supportedCities": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "city",
+    "localities",
+    "supported",
+    "comparison",
+    "attribution",
+    "handoffUrl",
+    "disclaimer"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJun 9, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
First observedMay 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: city coverage is limited to cities with published locality guides, unsupported cities return supported=false, and the agent should surface scopeMessage. It stops short of describing result shape or any latency/limit behavior, but the failure-mode disclosure is substantive.

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

Conciseness4/5

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

Three sentences, front-loaded with the capability before the routing guidance, and no filler. It is information-dense — scope, trigger, failure mode, and alternative all compressed — which is efficient though slightly crowded for a single paragraph.

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

Completeness5/5

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

With an output schema present, return-value explanation is unnecessary, and the description covers what the schema cannot: supported-city scope, the supported=false / scopeMessage path, and the sibling routing rule. Nothing an agent needs to select and call this tool correctly is missing.

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 description coverage is 100%, so city, localities, and propertyType are already documented, including the array-not-comma-separated constraint and the 2–3 bound. The description reinforces the one-city scope and the 2–3 count but adds no syntax or semantics for propertyType. Baseline 3 applies when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (compare) and resource (2–3 localities in one city) and enumerates the output dimensions: price trends, livability, investment grade, strengths, watchouts. It explicitly distinguishes itself from the sibling compare_properties, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit triggering conditions (user asks "X vs Y" or "which is better for buying/renting" about neighborhoods) and names the alternative plus the condition that selects it: "For specific LISTINGS by ID, use compare_properties instead." When-to-use and when-not-to-use are both present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AVnester — Indian Real Estate Intelligence tools Inspect

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.

Resources

Need Help?