Skip to main content
Glama

normi

by io.github.NormiHQ
OverviewDiscussionsAdmin

Search Property Transactions

search_property_transactions
Read-only

Search French property transactions (Demandes de Valeurs Foncières).

REQUIRED: You MUST provide at least one location filter:

  • code_postal (e.g., "75011" for Paris 11e)

  • commune (e.g., "PARIS 11", "LYON", "MARSEILLE" - uppercase; Paris uses arrondissements: "PARIS 01"–"PARIS 20")

  • code_departement (e.g., "75" for Paris, "69" for Rhône)

  • latitude + longitude for radius search (e.g., 48.8566, 2.3522 for Paris center)

  • address + code_postal for automatic geocoding (e.g., address: "12 rue de Rivoli", code_postal: "75001")

Common examples:

  • Paris 11e apartments: {commune: "PARIS 11", type_local: "Appartement"}

  • Near a location: {latitude: 48.8566, longitude: 2.3522, radius_m: 500}

  • By postal code: {code_postal: "69001", type_local: "Maison"}

  • By address: {address: "12 rue de Rivoli", code_postal: "75001", radius_m: 300}

Options:

  • summary_only=true: Get stats + 3 samples (~500 tokens vs ~3500 for full results) — use this for overviews. The stats cover every matching sale, identical to analyze_market_statistics (same date cap), unless prix_*/surface_*/pieces_min filters are set: then summary.basis = "sample" and they describe the returned page only.

  • limit: 1-100 results (default: 5)

  • type_local: "Appartement", "Maison", "Terrain", "Local commercial"

Note: radius_m > 1000m is automatically restricted to the last 12 months of data.

Cost: 5 credits per call

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results (default: 5)
offsetNoOffset for pagination
addressNoStreet address for automatic geocoding — alternative to explicit lat/lon. Example: '12 rue de Rivoli'. Best used with code_postal for precision. Resolves via api-adresse.data.gouv.fr.
communeNoCity/commune name (e.g., 'Paris', 'Lyon')
date_finNoEnd date (YYYY-MM-DD)
latitudeNoLatitude for radius search (requires longitude)
prix_maxNoMaximum price in EUR
prix_minNoMinimum price in EUR
radius_mNoRadius in meters for location search (default: 500)
longitudeNoLongitude for radius search (requires latitude)
date_debutNoStart date (YYYY-MM-DD)
pieces_minNoMinimum number of rooms
type_localNoProperty type
code_postalNoPostal code (e.g., '75001')
deduplicateNoGroup duplicate sales (same date, address, price) into single entries
surface_maxNoMaximum surface area in m²
surface_minNoMinimum surface area in m²
exclude_vefaNoExclude VEFA (new-build, vente en l'état futur d'achèvement) sales (default: true — keeps 'ancien' results from double-counting new-build activity)
summary_onlyNoReturn only summary statistics with 3 sample transactions instead of full list (reduces context usage)
code_departementNoDepartment code (e.g., '73' for Savoie, '83' for Var)
use_original_typeNoUse original type_local instead of smart computed_type_local (default: false)
exclude_bulk_salesNoExclude bulk sales and aggregated transactions (default: true for clean market data)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / exclude_outliers
      Removed value: -{
-  "default": true,
-  "description": "Exclude price outliers (default: true for clean market data)",
-  "type": "boolean"
-}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real behavioral context beyond them: a 5-credit cost per call, the automatic 12-month restriction on radius searches over 1000m, and the summary.basis='sample' vs full-stats distinction. It does not describe the return record shape, but the cost and silent-restriction disclosures are substantive.

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-loads the REQUIRED constraint, then examples, then options, then cost. Structure is excellent and each block is useful, though the examples section repeats filters already enumerated above it, adding some length for a 22-parameter tool.

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?

For a 22-parameter, no-output-schema search tool, the description covers the critical calling constraints (location requirement, pagination defaults via schema, summary mode, cost). Return-value shape is only lightly sketched, but the summary_only/full-results contrast covers the main ambiguity.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds constraints the schema cannot express: no parameter is marked required in the schema yet at least one location filter is mandatory, plus commune formatting quirks (uppercase, 'PARIS 01'–'PARIS 20') and worked filter examples. This meaningfully supplements the schema.

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 ('Search French property transactions (Demandes de Valeurs Foncières)') with scope. The DVF reference and location-filter framing make it clearly distinguishable from analytical siblings like analyze_market_statistics or find_property_comparables.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the mandatory precondition (at least one location filter) and enumerates the five valid filter combinations. It routes to alternatives in-line, telling the agent when to use summary_only ('for overviews') and how its stats relate to analyze_market_statistics, plus noting the radius_m>1000m date restriction.

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

All normi toolsInspect
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