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

TableJSON 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

TableJSON 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

Schema Changelog

Changes observed during successful MCP inspections.

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.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so safety is covered. The description adds genuinely new behavior: unsupported cities return supported=false and a scopeMessage the agent should surface. It does not describe result shape, but an output schema exists to cover that.

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 dense sentences, fully front-loaded: capability first, then trigger, then scope caveat and sibling routing. No filler and nothing that could be dropped without losing routing signal.

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?

For a read-only comparison tool with an output schema and full annotation coverage, the description supplies the remaining gaps an agent needs: input cardinality, trigger phrasing, scope failure mode, and sibling disambiguation.

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 the schema already documents all three parameters. The description adds the same-city constraint ('2–3 localities in one city') and the supported-city scope, but nothing about propertyType or value formats beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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+resource ('Compare 2–3 localities in one city side-by-side') and enumerates what is compared: price trends, livability, investment grade, strengths, watchouts. It explicitly distinguishes itself from compare_properties, which handles listings by ID.

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 an explicit trigger ('X vs Y', 'which is better for buying/renting'), names the alternative tool with the condition that selects it, and states scope limits for unsupported cities with the supported=false/scopeMessage fallback.

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?