Skip to main content
Glama

dvf_price_m2

Get official DVF French property price per m² for an address, with median, p25/p75, and sale counts for apartments and houses over the last 3 years. Optionally add surface and property type to estimate value.

Instructions

French property price per m2 around an address from official DVF sales records (DGFiP / Etalab, last 3 years): median, p25/p75, count for apartments and houses within an auto-expanding radius, geocoded via Base Adresse Nationale. Not available for Alsace-Moselle and Mayotte. Costs 0.01 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": {
      "address": "<address>"
    },
    "name": "dvf_price_m2"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesFrench street address
surfaceNooptional surface in m2 for an estimate
propertyTypeNooptional: Appartement or Maison

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses a cost of 0.01 USDC on Base via x402, the 402 response without a payment key, the 3-year data window, the auto-expanding radius, the geocoding dependency on Base Adresse Nationale, and the coverage gaps. Remaining gaps are error behavior beyond the 402 and any rate limits or determinism notes.

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?

Front-loaded with purpose and output shape before caveats and pricing, which is the right order. It is dense but every clause carries information; the parenthetical source and contract details are the least essential parts but still relevant to an agent deciding whether to call.

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?

No output schema exists, and the description compensates by listing the statistics returned and the radius behavior. Cost, payment failure mode, and geographic exclusions are all covered; what remains thin is the shape of the returned data (per-type breakdown, units of radius/coverage) and non-payment error paths.

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 address, surface, and propertyType; baseline is 3. The description adds no syntax or behavior detail for the optional surface estimate or the propertyType values, and the auto-expanding radius behavior is not tied to any parameter.

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 and resource — property price per m2 around an address — names the authoritative source (DVF, DGFiP/Etalab, last 3 years), and enumerates the returned statistics (median, p25/p75, count). An agent can distinguish this from address/geocoding siblings like fr_address without opening the schema.

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 when-not conditions (not available for Alsace-Moselle and Mayotte) and the prerequisite for a successful call (a payment key; otherwise a 402 challenge). It does not name an alternative tool for out-of-coverage departments or for non-price address needs, so it stops short of full routing guidance.

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