Skip to main content
Glama

Lexou · droit français

Prix des ventes immobilières d'une commune (DVF)

prix_immobiliers_dvf
Read-onlyIdempotent

Ventes immobilières publiées par la DGFiP (demandes de valeurs foncières) pour une commune : nombre de ventes, prix médian, minimum, maximum, prix médian au m² et ventes récentes. Pas pour estimer un bien précis.

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": {
      "code_postal": "<code_postal>"
    },
    "name": "prix_immobiliers_dvf"
  }
}

Input Schema

NameRequiredDescriptionDefault
villeNo
code_postalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4/5.0
Behavior4/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=true, so safety is covered. The description adds real value beyond them by naming the data source (DGFiP/DVF) and listing the returned aggregates, though it omits known behavioral limits of DVF data (only recorded sales, publication lag, coverage gaps for some communes).

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 short sentences, front-loaded with the resource and data source, then the metric list, then the scope exclusion. Dense but readable; the metric enumeration earns its place since there is no output schema, though it could be slightly tighter.

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, listing the returned metrics is necessary and done well, and the data source is identified. The main gap is the total absence of parameter guidance for a tool whose schema has 0% description coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden, and it says nothing about the two parameters. It never explains whether code_postal alone is sufficient, what 'ville' adds, or how the optional ville interacts with the required 5-digit code_postal, leaving the caller to guess whether to supply both.

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+resource (real-estate sales from DGFiP/DVF for a commune) and enumerates exactly what is returned: number of sales, median/min/max price, median price per m², recent sales. The closing 'Pas pour estimer un bien précis' sharply bounds the scope, so an agent knows immediately this is aggregate market data, not a valuation tool.

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 a clear when-to-use context ('pour une commune') and one explicit when-not-to-use ('pas pour estimer un bien précis'), which is the most plausible misuse. No alternative tool is named for the excluded valuation case, and it doesn't mention constraints such as only sold properties being covered or data freshness.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources