AVnester — Indian Real Estate Intelligence

Get locality market insights

get_locality_insights

Read-onlyIdempotent

Get aggregated insights for one locality: ₹/sqft, supply count, demand pulse, livability/investment grade, highlights, watchouts, monthly priceTrends, and strengthTags. Use when the user asks "what is X locality like". Covers cities AVnester publishes locality guides for; others return supported=false — surface the scopeMessage. Always surface the disclaimer field when returning livability or investment grade.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	Yes	Indian city (required).
`locality`	Yes	Locality name within an Indian city.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`city`	Yes
`cards`	Yes
`message`	No
`insights`	Yes
`locality`	Yes
`freshness`	Yes
`supported`	Yes
`disclaimer`	Yes
`handoffUrl`	Yes
`attribution`	Yes
`scopeMessage`	No
`supportedCities`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed6 schema fields changedSep 23, 2026

addedOutput schema / properties / insights / properties / livabilityScoreBasis

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

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

changedOutput schema / properties / insights / required

Previous value: -[
-  "avgPriceInr",
-  "supplyCount",
-  "demandPulse",
-  "livabilityScore",
-  "investmentGrade",
-  "highlights",
-  "watchouts",
-  "priceTrends",
-  "strengthTags"
-]New value: +[
+  "avgPriceInr",
+  "pricePerSqftInr",
+  "rent2bhkInr",
+  "rentalYieldPct",
+  "priceGrowth1YPct",
+  "supplyCount",
+  "demandPulse",
+  "livabilityScore",
+  "livabilityScoreBasis",
+  "investmentGrade",
+  "highlights",
+  "watchouts",
+  "priceTrends",
+  "strengthTags"
+]

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",
-  "locality",
-  "supported",
-  "insights",
-  "freshness",
-  "attribution",
-  "handoffUrl",
-  "disclaimer"
-]New value: +[
+  "city",
+  "locality",
+  "supported",
+  "insights",
+  "freshness",
+  "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"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "freshness": {
+      "additionalProperties": true,
+      "properties": {
+        "confidence": {
+          "enum": [
+            "high",
+            "medium",
+            "low"
+          ],
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "sourceCount": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "updatedAt": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "updatedAt",
+        "sourceCount",
+        "confidence"
+      ],
+      "type": "object"
+    },
+    "handoffUrl": {
+      "format": "uri",
+      "type": "string"
+    },
+    "insights": {
+      "additionalProperties": true,
+      "properties": {
+        "avgPriceInr": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "demandPulse": {
+          "enum": [
+            "low",
+            "medium",
+            "high"
+          ],
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "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"
+        },
+        "supplyCount": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "watchouts": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "avgPriceInr",
+        "supplyCount",
+        "demandPulse",
+        "livabilityScore",
+        "investmentGrade",
+        "highlights",
+        "watchouts",
+        "priceTrends",
+        "strengthTags"
+      ],
+      "type": "object"
+    },
+    "locality": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "scopeMessage": {
+      "type": "string"
+    },
+    "supported": {
+      "type": "boolean"
+    },
+    "supportedCities": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "city",
+    "locality",
+    "supported",
+    "insights",
+    "freshness",
+    "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.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds two genuinely useful behavioral contracts beyond that: unsupported cities return supported=false with a scopeMessage to surface, and the disclaimer field must always be surfaced with livability/investment grades.

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?

Compact and front-loaded: the field inventory comes first, then the trigger, then scope and disclaimer obligations. The field list is slightly dense, but no sentence is wasted.

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?

An output schema exists, so return values need not be explained, yet the description adds the coverage boundary (supported=false/scopeMessage) and the mandatory disclaimer behavior an agent must honor. Combined with the fully documented two-parameter schema, it is nearly complete for this tool's complexity.

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% and both required parameters (city, locality) carry their own schema descriptions, so the description adds no syntax, format, or matching nuance beyond the structured data. Baseline 3 is appropriate 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 and resource ('get aggregated insights for one locality') and enumerates the returned attributes (₹/sqft, supply count, demand pulse, grades, priceTrends, strengthTags). This clearly separates it from the plural sibling compare_localities 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 Guidelines4/5

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

Gives an explicit trigger ('Use when the user asks "what is X locality like"') plus scope guidance (only cities AVnester publishes guides for) and the fallback behavior for unsupported cities. It does not name compare_localities as the alternative for multi-locality questions, so routing between the two is left partly to inference.

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?