Skip to main content
Glama
AgentIA1984-cmd

MCP Immobilier France (DVF)

Estimate French property value (DVF comparables)

fr_property_price_estimate
Read-onlyIdempotent

Estimate a French property's market value by analyzing comparable recent sales nearby, with price per square meter and confidence range.

Instructions

Estimate the market value of a French property using comparable DVF sales (same type, similar surface, nearby, recent).

Method: geocode the address, select comparable sales within 'radius_m' of the same 'property_type' with a built surface within ±35% and sold within 'years_back' years, then apply the median EUR/m² to the property's surface. Returns a point estimate and a p25-p75 range with a confidence level based on the number of comparables.

Args:

  • address (string): property address

  • surface_m2 (number): built surface in m²

  • property_type (string): 'Appartement' (default) or 'Maison', etc.

  • radius_m (number): comparable radius in metres (default 500)

  • years_back (number): lookback window in years (default 5)

  • response_format ('markdown' | 'json'): output format

Returns: estimate (EUR), low/high range (EUR), median/p25/p75 EUR/m², comps count, confidence ('high'|'medium'|'low'|'insufficient'). This is a statistical estimate, not a certified valuation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesAddress of the property to estimate.
radius_mNoRadius for comparable selection, metres (50-5000).
surface_m2YesBuilt surface of the property in square metres.
years_backNoHow many years of past sales to consider (default 5).
property_typeNoProperty type to compare against, e.g. 'Appartement' or 'Maison'.Appartement
response_formatNoOutput format: 'markdown' (human) or 'json' (machine).markdown
Behavior5/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable context: it details the estimation methodology (geocode, ±35% surface, median EUR/m²), warns it's a statistical estimate not certified, and explains confidence levels. This goes beyond annotations.

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?

The description is well-structured: purpose sentence, method paragraph, args list, returns. It is front-loaded and every sentence adds value, including the caveat about statistical estimate. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description thoroughly explains return values (estimate, range, comps count, confidence) and the method. It covers the algorithmic details, default values, and limitations (not certified valuation), making it fully actionable for an agent.

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% (6/6 parameters described in schema). The description adds methodological context (e.g., radius_m for comparable selection, years_back lookback) but does not significantly enhance individual parameter meanings beyond what the schema already provides. Baseline 3 is appropriate.

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 clearly states it estimates the market value of a French property using DVF comparables, specifying the verb (estimate) and resource (French property). It distinguishes from sibling tools like geocode or transactions by focusing on valuation.

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?

The description explains the method and what the tool does, but does not explicitly state when to use it over alternatives like fr_property_market_stats or fr_property_transactions. However, the purpose is clear enough for an agent to infer usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AgentIA1984-cmd/mcp-immobilier-dvf'

If you have feedback or need assistance with the MCP directory API, please join our Discord server