Parcellaire — cadastre, DVF & DPE

Détails d'une parcelle cadastrale

get_parcelle

Read-onlyIdempotent

Retourne les informations d'une parcelle cadastrale à partir de son IDU (14 caractères) : surface, adresse, parcelles adjacentes (qui la touchent, avec surface, bâti et nombre de DPE), et selon 'include' les bâtiments, transactions immobilières (dvf), diagnostics énergétiques (dpes), zonage d'urbanisme (urbanisme), données bâtiment BDNB (bdnb), piscines, copropriétés (rnc), propriétaires personnes morales (majic_pm), permis de construire (sitadel).

Input Schema

TableJSON Schema

Name	Required	Description
`include`	No	Sections à inclure. Défaut: ['batiments', 'dvf', 'dpes']
`max_items`	No	Nombre maximum d'éléments par section liste (défaut 30). Les sections tronquées sont signalées dans 'sections_tronquees'.
`parcelle_id`	Yes	IDU de la parcelle, 14 caractères, ex: '33063000IK0001'

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed7 schema fields changedSep 25, 2026

addedInput schema / properties / include / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "items": {
+          "enum": [
+            "batiments",
+            "dvf",
+            "dpes",
+            "urbanisme",
+            "bdnb",
+            "piscines",
+            "rnc",
+            "majic_pm",
+            "sitadel"
+          ],
+          "type": "string"
+        },
+        "type": "array"
+      },
+      {
+        "const": "",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / include / items

Removed value: -{
-  "enum": [
-    "batiments",
-    "dvf",
-    "dpes",
-    "urbanisme",
-    "bdnb",
-    "piscines",
-    "rnc",
-    "majic_pm",
-    "sitadel"
-  ],
-  "type": "string"
-}

removedInput schema / properties / include / type
```
Removed value: -"array"
```

addedInput schema / properties / max_items / anyOf

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

removedInput schema / properties / max_items / maximum
```
Removed value: -200
```
removedInput schema / properties / max_items / minimum
```
Removed value: -1
```
removedInput schema / properties / max_items / type
```
Removed value: -"integer"
```

First observedSep 25, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: it enumerates the returned sections (surface, address, adjacent parcels with details) and explains that the 'include' parameter controls which optional datasets are returned.

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?

The description is a single sentence that front-loads the core action and then compactly lists the include options. The list is partly redundant with the schema enum, but it serves as a useful quick summary; splitting it into shorter sentences would improve readability.

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 lookup tool with three parameters and no output schema, the description is sufficiently complete: it specifies the required IDU, the optional include sections, and the main output categories. It does not describe output formatting, but the schema covers parameters and annotations cover side effects.

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 context for parcelle_id and lists the include options, but it adds no additional meaning for max_items beyond what the schema provides.

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 ('Retourne') and resource ('une parcelle cadastrale') and identifies the exact lookup key (IDU). This makes the tool's scope clear and distinguishes it from sibling search tools like search_parcelles or find_parcelles_by_address.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies the tool is for retrieving a single parcel's details when the IDU is already known, but it does not explicitly state when to prefer it over alternatives such as search_parcelles or get_parcelle_context. No exclusions or alternative routing are provided.

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?