Parcellaire — cadastre, DVF & DPE

Rechercher des DPE dans une zone

search_dpe

Read-onlyIdempotent

Liste les diagnostics de performance énergétique (DPE ADEME) d'une zone : autour d'une adresse, d'une parcelle ou d'un point (rayon), ou dans toute une commune. Filtres : type de bâtiment, classes énergie/GES, surface, année de construction, date du DPE. Avec 'address' (numéro + rue), retourne aussi les DPE rattachés exactement à cette adresse. Résultats triés du plus récent au plus ancien et paginés ('limit', 'offset').

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Latitude du centre (avec 'lng')
`lng`	No	Longitude du centre (avec 'lat')
`limit`	No	DPE 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)
`classe_dpe`	No
`classe_ges`	No
`parcelle_id`	No	IDU d'une parcelle au centre de la zone
`date_dpe_max`	No	Date maximale du DPE, 'AAAA-MM-JJ'
`date_dpe_min`	No	Date minimale du DPE, 'AAAA-MM-JJ'
`type_batiment`	No	'immeuble' = DPE d'immeuble collectif entier
`surface_max_m2`	No
`surface_min_m2`	No
`annee_construction_max`	No
`annee_construction_min`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed50 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 / annee_construction_max / anyOf

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

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

addedInput schema / properties / annee_construction_min / anyOf

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

removedInput schema / properties / annee_construction_min / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / annee_construction_min / minimum
```
Removed value: --9007199254740991
```
removedInput schema / properties / annee_construction_min / 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 / classe_ges / anyOf

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

removedInput schema / properties / classe_ges / enum

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

removedInput schema / properties / classe_ges / 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_dpe_max / anyOf

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

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

addedInput schema / properties / date_dpe_min / anyOf

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

removedInput schema / properties / date_dpe_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 / 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 / type_batiment / anyOf

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

removedInput schema / properties / type_batiment / enum

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

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

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 declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is clear. The description adds useful behavioral context: results are sorted newest to oldest, paginated with limit/offset, and the 'address' mode returns exact matches. It doesn't mention rate limits or response format, but the annotations cover the main safety aspects.

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 concise and well-structured: it states the core function, lists filters, highlights special behavior for 'address', and mentions sorting and pagination. Every sentence adds value without redundancy.

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 17 parameters and no output schema, the description covers the main usage modes, filters, sorting, and pagination. It doesn't explain the response structure (since no output schema exists), but the description is sufficient for an agent to invoke the tool correctly. Minor gaps: no mention of how to combine parameters or what happens with conflicting modes (e.g., address vs commune).

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 59%, so the description partially compensates. It explains the meaning of key parameters (address, commune, rayon_m, type_batiment, date_dpe_min/max) and adds context like 'immeuble' meaning whole building DPE. However, some parameters like surface_min_m2, surface_max_m2, annee_construction_min/max, offset, classe_dpe, classe_ges lack description-level detail, though their names are fairly self-explanatory.

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 clearly states the tool's purpose: listing DPE diagnostics in a zone, with specific search modes (address, parcel, point with radius, commune) and filters. It distinguishes itself from sibling tools like get_dpe (which likely retrieves a single DPE) by emphasizing the zone-based search and listing behavior.

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 explains the different search modes (address, parcel, point, commune) and notes that 'commune' ignores 'rayon_m', and that 'address' returns exact matches. However, it doesn't explicitly state when to prefer this over siblings like search_parcelles or get_dpe, nor does it mention exclusions or alternatives.

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?