Parcellaire — cadastre, DVF & DPE

Ventes immobilières (DVF) dans une zone

search_ventes_dvf

Read-onlyIdempotent

Liste les ventes immobilières (DVF) d'une zone : autour d'une adresse, d'une parcelle ou d'un point (rayon), ou dans toute une commune — idéal pour trouver des biens comparables. Une ligne par vente : date, prix, type de bien, surface bâtie, pièces, terrain, parcelles, prix au m² (quand la vente porte sur un seul logement). Retourne aussi la médiane du prix au m² des ventes filtrées. Seules les ventes géolocalisées sont couvertes (depuis 2021). Filtrer par 'type_bien' pour des prix au m² comparables.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Latitude du centre (avec 'lng')
`lng`	No	Longitude du centre (avec 'lat')
`tri`	No	Tri des ventes (défaut : date décroissante ; distance pour les plus proches)
`limit`	No	Ventes par page (défaut 20, max 50)
`offset`	No
`address`	No	Adresse postale au centre de la zone
`commune`	No	Nom de commune : toute la commune (ignore 'rayon_m')
`rayon_m`	No	Rayon autour du centre en mètres (défaut 500, max 2000)
`date_max`	No	Date maximale 'AAAA-MM-JJ'
`date_min`	No	Date minimale 'AAAA-MM-JJ' (défaut 2021-01-01)
`type_bien`	No
`parcelle_id`	No	IDU d'une parcelle au centre de la zone
`prix_max_eur`	No
`prix_min_eur`	No
`surface_max_m2`	No
`surface_min_m2`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed1 schema field changedSep 25, 2026

changedInput schema / properties / tri / description

Previous value: -"Tri des ventes (défaut : distance autour d'un point, date pour une commune)"New value: +"Tri des ventes (défaut : date décroissante ; distance pour les plus proches)"

Changed45 schema fields changedSep 25, 2026

addedInput schema / properties / address / anyOf

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

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

addedInput schema / properties / commune / anyOf

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

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

addedInput schema / properties / date_max / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      },
+      {
+        "const": "",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / date_max / pattern
```
Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
```
removedInput schema / properties / date_max / type
```
Removed value: -"string"
```

addedInput schema / properties / date_min / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      },
+      {
+        "const": "",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / date_min / pattern
```
Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
```
removedInput schema / properties / date_min / 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 / limit / anyOf

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

removedInput schema / properties / limit / maximum
```
Removed value: -50
```
removedInput schema / properties / limit / minimum
```
Removed value: -1
```
removedInput schema / properties / limit / type
```
Removed value: -"integer"
```

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 / offset / anyOf

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

removedInput schema / properties / offset / maximum
```
Removed value: -5000
```
removedInput schema / properties / offset / minimum
```
Removed value: -0
```
removedInput schema / properties / offset / type
```
Removed value: -"integer"
```

addedInput schema / properties / parcelle_id / anyOf

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

removedInput schema / properties / parcelle_id / maxLength
```
Removed value: -14
```
removedInput schema / properties / parcelle_id / minLength
```
Removed value: -14
```
removedInput schema / properties / parcelle_id / type
```
Removed value: -"string"
```

addedInput schema / properties / prix_max_eur / anyOf

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

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

addedInput schema / properties / prix_min_eur / anyOf

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

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

addedInput schema / properties / rayon_m / anyOf

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

removedInput schema / properties / rayon_m / maximum
```
Removed value: -2000
```
removedInput schema / properties / rayon_m / minimum
```
Removed value: -50
```
removedInput schema / properties / rayon_m / type
```
Removed value: -"integer"
```

addedInput schema / properties / surface_max_m2 / anyOf

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

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

addedInput schema / properties / surface_min_m2 / anyOf

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

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

addedInput schema / properties / tri / anyOf

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

removedInput schema / properties / tri / enum

Removed value: -[
-  "date",
-  "distance"
-]

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

addedInput schema / properties / type_bien / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "enum": [
+          "maison",
+          "appartement",
+          "local"
+        ],
+        "type": "string"
+      },
+      {
+        "const": "",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / type_bien / enum

Removed value: -[
-  "maison",
-  "appartement",
-  "local"
-]

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

First observedSep 25, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds substantial behavioral detail: one row per sale with listed fields, the conditional price-per-m² field when the sale involves a single dwelling, a median price-per-m² summary, and the coverage limitation since 2021. No contradiction with annotations.

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 dense but efficient: five sentences, each adding meaningful information—scope, output shape, summary metric, coverage limitation, and a filtering tip. The main action and use case are front-loaded, with no filler words.

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?

For a read-only search tool with no output schema, the description covers the core answer: row-level fields, median metric, geographic modes, time coverage, and filter guidance. It does not mention pagination or limit/offset behavior, and it omits some filter semantics, but those are partially present in the schema and the description carries most of the decision-relevant context.

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 coverage is 63%, so the schema already documents a majority of parameters. The description adds practical framing for the main selectors (address, parcelle, rayon, commune) and a useful note about type_bien, but it does not clarify the price, surface, date, or pagination parameters beyond what the schema provides. Helpful but not a full compensation for the remaining undocumented fields.

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 states a specific verb and resource: 'Liste les ventes immobilières (DVF) d'une zone', and immediately enumerates the geographic modes (address, parcelle, point/rayon, whole commune). This clearly distinguishes it from sibling tools like search_dpe, search_parcelles, or estimate_property_price.

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?

It names the intended use case, 'idéal pour trouver des biens comparables', and gives a concrete selection tip: filter by type_bien for comparable price per m². It also states an important exclusion—only geolocalized sales since 2021. It does not explicitly name sibling alternatives, but the guidance is sufficient for an agent to choose this tool.

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?