Parcellaire — cadastre, DVF & DPE

Estimer le prix d'un bien immobilier

estimate_property_price

Read-onlyIdempotent

Estime le prix de vente d'une maison ou d'un appartement en France à partir des transactions DVF récentes et d'un modèle statistique national. Localisation par 'address' OU par 'lat' + 'lng' + 'code_insee'. Retourne un prix total, une fourchette, un prix au m² et des facteurs explicatifs.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Latitude, si pas d'adresse
`lng`	No	Longitude, si pas d'adresse
`address`	No	Adresse du bien (option la plus simple)
`type_bien`	Yes
`classe_dpe`	No	Classe DPE si connue (affine l'estimation)
`code_insee`	No	Code INSEE de la commune, si pas d'adresse
`surface_m2`	Yes	Surface habitable en m²
`terrain_m2`	No	Surface du terrain en m² (maisons)
`annee_construction`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed19 schema fields changedSep 25, 2026

addedInput schema / properties / address / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "const": "",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / address / type
```
Removed value: -"string"
```

addedInput schema / properties / annee_construction / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      {
+        "const": "",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / annee_construction / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / annee_construction / minimum
```
Removed value: --9007199254740991
```
removedInput schema / properties / annee_construction / type
```
Removed value: -"integer"
```

addedInput schema / properties / classe_dpe / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "enum": [
+          "A",
+          "B",
+          "C",
+          "D",
+          "E",
+          "F",
+          "G"
+        ],
+        "type": "string"
+      },
+      {
+        "const": "",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / classe_dpe / enum

Removed value: -[
-  "A",
-  "B",
-  "C",
-  "D",
-  "E",
-  "F",
-  "G"
-]

removedInput schema / properties / classe_dpe / type
```
Removed value: -"string"
```

addedInput schema / properties / code_insee / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "maxLength": 5,
+        "minLength": 5,
+        "type": "string"
+      },
+      {
+        "const": "",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / code_insee / maxLength
```
Removed value: -5
```
removedInput schema / properties / code_insee / minLength
```
Removed value: -5
```
removedInput schema / properties / code_insee / type
```
Removed value: -"string"
```

addedInput schema / properties / lat / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "const": "",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / lat / type
```
Removed value: -"number"
```

addedInput schema / properties / lng / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "const": "",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / lng / type
```
Removed value: -"number"
```

addedInput schema / properties / terrain_m2 / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "const": "",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / terrain_m2 / type
```
Removed value: -"number"
```

First observedSep 25, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive behavior, so the description does not need to restate that. It adds meaningful behavioral detail beyond annotations: the estimate is based on recent DVF transactions and a national statistical model, returns a price range, and includes explanatory factors. This helps the agent understand the nature and limitations of the result without claiming precision.

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?

The description is two compact sentences that front-load the purpose, then present the two localization alternatives, then enumerate the return contents. Every clause adds information; there is no tautology or restatement of the title.

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?

There is no output schema, so the description usefully enumerates the returned items: total price, range, price per m², and explanatory factors. It also explains the data source and the main input alternatives. It does not discuss what happens if both address and lat/lng are supplied, but given the schema and annotations, the description is sufficient for correct invocation in most cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 78%, so most parameters are already documented in the schema. The description adds critical non-schema semantics by encoding the exclusive localization modes: address OR lat + lng + code_insee. This constraint is not expressed in the JSON Schema and is essential for making a valid call.

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?

The description opens with a specific verb ('Estime') and a precisely defined resource: the sale price of a house or apartment in France. It names the data sources (recent DVF transactions, national statistical model) and distinguishes itself from siblings like search_ventes_dvf by estimating rather than returning raw transaction data. The stated outputs (total price, range, price per m², explanatory factors) make the tool's role unmistakable.

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?

The description gives clear usage context: use it to get a property price estimate rather than transaction listings. It also spells out the two accepted localization modes (address or lat + lng + code_insee). It does not explicitly name sibling alternatives or exclusion conditions, but the contrast with the sibling set is clear enough for an agent to select this tool correctly.

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

All Parcellaire — cadastre, DVF & DPE 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?