Parcellaire — cadastre, DVF & DPE

Environnement d'une parcelle

get_parcelle_context

Read-onlyIdempotent

Retourne l'environnement d'une parcelle cadastrale (IDU 14 caractères) à partir de sources publiques (Géorisques, ARCEP, ministère de l'Éducation, observatoires des loyers…). Passer à true uniquement les sections utiles à la question, ex: { risques: true, fibre: true }. Sans aucune section à true, aucune donnée d'environnement n'est retournée.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "parcelle_id": "<parcelle_id>"
    },
    "name": "get_parcelle_context"
  }
}

Input Schema

Name	Required	Description
`air`	No	Indice de qualité de l’air et date de validité
`fibre`	No	Éligibilité fibre et opérateurs (ARCEP)
`sante`	No	Médecins, pharmacies… proches
`ecoles`	No	Écoles proches
`loyers`	No	Loyers de référence en €/m²
`emprise`	No	Emprise du bâti au sol
`risques`	No	Risques Géorisques : inondation, argiles, radon, sismicité, pollution…
`terrain`	No	Relief et altitude
`antennes`	No	Antennes mobiles proches, sans garantie de couverture
`prix_eau`	No	Prix déclarés des services d’eau desservant la commune
`recharge`	No	Bornes de recharge proches
`commerces`	No	Commerces proches
`filiation`	No	Historique des découpages cadastraux
`fiscalite`	No	Taux de fiscalité de la commune, pas une taxe foncière individuelle
`max_items`	No	Lignes par liste de risques et lieux par catégorie (défaut 5, max 100). Les listes partielles portent tronque et leurs comptes ; augmenter pour plus de détails. Les règles d’eau restent complètes.
`transports`	No	Arrêts de transport proches, sans horaires temps réel
`delinquance`	No	Délinquance enregistrée à l’échelle de la commune
`parcelle_id`	Yes	IDU de la parcelle, 14 caractères, ex: '33063000IK0001'
`restrictions_eau`	No	Arrêtés de restriction d'eau (sécheresse) en cours
`secteur_scolaire`	No	Établissements du secteur scolaire

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 3, 2026

addedInput schema / properties / air

Added value: +{
+  "description": "Indice de qualité de l’air et date de validité",
+  "type": "boolean"
+}

addedInput schema / properties / antennes

Added value: +{
+  "description": "Antennes mobiles proches, sans garantie de couverture",
+  "type": "boolean"
+}

addedInput schema / properties / delinquance

Added value: +{
+  "description": "Délinquance enregistrée à l’échelle de la commune",
+  "type": "boolean"
+}

addedInput schema / properties / fiscalite

Added value: +{
+  "description": "Taux de fiscalité de la commune, pas une taxe foncière individuelle",
+  "type": "boolean"
+}

addedInput schema / properties / prix_eau

Added value: +{
+  "description": "Prix déclarés des services d’eau desservant la commune",
+  "type": "boolean"
+}

addedInput schema / properties / transports

Added value: +{
+  "description": "Arrêts de transport proches, sans horaires temps réel",
+  "type": "boolean"
+}

Changed1 schema field changedOct 31, 2026

addedInput schema / properties / max_items

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "maximum": 100,
+          "minimum": 1,
+          "type": "integer"
+        },
+        {
+          "const": "",
+          "type": "string"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Lignes par liste de risques et lieux par catégorie (défaut 5, max 100). Les listes partielles portent tronque et leurs comptes ; augmenter pour plus de détails. Les règles d’eau restent complètes."
+}

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

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description contributes real behavioral context beyond that: the all-false case returns no environment data at all, and the data provenance is enumerated. It says nothing about response shape or how truncated lists are surfaced.

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?

Three sentences, front-loaded with the core purpose, then the flag-selection rule, then the empty-result caveat. No filler and nothing buried.

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 20-parameter read-only aggregation tool with no output schema, the description covers purpose, selective activation, and the zero-selection edge case adequately. It omits any indication of return structure or how partial/truncated results appear, which matters slightly given the absent output schema.

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 100%, so the schema already documents all 19 flags and max_items in detail; that sets the baseline at 3. The description reinforces the selection semantics with a concrete example and the all-false consequence, but adds little meaning the schema does not already carry.

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 ("Retourne") plus a precise resource ("l'environnement d'une parcelle cadastrale") and scope ("sources publiques" with named providers). The word "environnement" cleanly separates it from siblings like get_parcelle (the parcel record itself) and get_commune_stats (commune-level data).

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 explicit operating guidance: enable only the sections relevant to the question, with an example payload, and warns that enabling nothing yields no data. It stops short of stating when to prefer this over get_parcelle or get_commune_stats, so routing between siblings is left to inference.

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?