Skip to main content
Glama
AgentIA1984-cmd

MCP Immobilier France (DVF)

List French property sales (DVF)

fr_property_transactions
Read-onlyIdempotent

List recent French real estate sale transactions near an address or within a commune, with filters for property type, rooms, and year. Sorted most recent first.

Instructions

List recorded real-estate sale transactions from the French DVF open dataset, near an address or within a commune.

Provide EITHER 'address' (recommended — enables radius search) OR 'citycode' (INSEE, whole commune).

Args:

  • address (string, optional): address to search around

  • citycode (string, optional): INSEE commune code (5 chars)

  • radius_m (number): radius around the address in metres (default 500)

  • property_type (string, optional): e.g. 'Maison', 'Appartement'

  • since_year (number, optional): earliest sale year (>= 2010)

  • min_rooms / max_rooms (number, optional): room-count filter

  • limit (number): max results, 1-200 (default 50)

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

Returns: sales with date, price (EUR), property type, surface (m2), rooms, price/m2, address, commune. Sorted most-recent first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of transactions to return (1-200).
addressNoAddress to search around (recommended). Either 'address' or 'citycode' is required.
citycodeNoINSEE commune code (5 chars). Alternative to 'address'.
radius_mNoSearch radius in metres around the address (50-5000).
max_roomsNoMaximum number of main rooms.
min_roomsNoMinimum number of main rooms.
since_yearNoKeep only sales on/after January 1 of this year (DVF starts 2010).
property_typeNoFilter by property type substring, e.g. 'Maison' or 'Appartement'.
response_formatNoOutput format: 'markdown' (human) or 'json' (machine).markdown
Behavior4/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral details such as the return format (sales with fields, sorted most-recent first) and data source (DVF starts 2010), which go 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and key choice, followed by a clean argument list. It is concise for 9 parameters, with no extraneous information. Minor improvement could be a more structured list, but overall efficient.

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?

Given the tool's complexity (9 parameters, no output schema), the description covers all necessary aspects: data source, required conditions, filtering options, return fields, sorting, and format. Annotations further cover safety and idempotency, making the description complete for an agent to use effectively.

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

Parameters4/5

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

With 100% schema coverage, the description still adds value by clarifying the mutual exclusivity of 'address' and 'citycode', emphasizing the default radius, and grouping parameters into logical categories (e.g., filtering by rooms, year). This provides meaning beyond the schema alone.

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 the tool lists real-estate sale transactions from the French DVF dataset, with options for address or commune. This specific verb+resource+scope distinguishes it from sibling tools like geocoding, market stats, or price estimates.

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 provides clear context on when to use the tool, advising to provide either 'address' or 'citycode'. It recommends 'address' for radius search. However, it does not explicitly mention when not to use it or directly reference sibling tools for alternatives.

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