Parcellaire — cadastre, DVF & DPE

Statistiques immobilières d'une commune

get_commune_stats

Read-onlyIdempotent

Retourne les statistiques d'une commune française : parcelles et bâtiments, prix au m² et volumes de transactions DVF par année, répartition des classes DPE, taux de propriétaires, logements vacants, etc. Identifier la commune par 'insee_id' (fiable) ou par 'commune' (nom ou code postal).

Input Schema

Name	Required	Description	Default
`commune`	No	Nom de la commune, ex: 'Angers'. Pour une commune homonyme, préciser son code entre parenthèses : 'Thénac (17444)' (code INSEE), 'Thénac (17460)' (code postal) ou 'Thénac (17)' (département). Ou son code postal.
`insee_id`	No	Code INSEE de la commune (prioritaire si fourni)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / commune / description

Previous value: -"Nom ou code postal de la commune, ex: 'Bordeaux'"New value: +"Nom de la commune, ex: 'Angers'. Pour une commune homonyme, préciser son code entre parenthèses : 'Thénac (17444)' (code INSEE), 'Thénac (17460)' (code postal) ou 'Thénac (17)' (département). Ou son code postal."

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

Changed6 schema fields changedSep 25, 2026

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

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

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

First observedSep 25, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds no behavioral context beyond that — no mention of response shape, handling of ambiguous or unknown communes, or data freshness — so it contributes almost nothing on this dimension.

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?

Two sentences, purpose front-loaded, parameter guidance second — no filler or repetition of the title. The trailing 'etc.' on an otherwise precise enumeration is the only soft spot, leaving the list slightly open-ended.

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?

With no output schema, the description carries the burden of describing returns and does so by listing the statistic families the caller will receive. It is nearly complete for a two-parameter, zero-required read tool; the remaining gap is how results are shaped or what happens when a commune cannot be resolved.

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 both parameters in detail, including the parenthetical disambiguation syntax and the 'prioritaire si fourni' rule. The description only echoes the preference for insee_id as reliable, adding marginal value over the structured fields, which matches the baseline 3 for full coverage.

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 names a specific verb and resource ('Retourne les statistiques d'une commune française') and then enumerates the exact content returned: parcelles/bâtiments, prix au m², volumes DVF par année, classes DPE, taux de propriétaires, logements vacants. That enumeration cleanly separates it from siblings like search_communes or get_parcelle, which return entities rather than aggregate statistics.

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?

It gives parameter-level routing advice ('insee_id' is reliable, 'commune' accepts name or postal code), which helps the agent choose an identifier but not whether to call this tool at all. There is no explicit when-to-use/when-not-to-use statement and no named alternative among the many siblings. Usage is only implied by the purpose.

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?