Skip to main content
Glama
Sign In

rundata.re · La Réunion en direct

by re.rundata
OverviewDiscussionsAdmin

Cadastre, urbanisme, prix immobiliers et risques à une adresse de La Réunion

fiche_terrain
Read-only

Ce que disent les registres officiels du bien ou du lieu de La Réunion (974) sur lequel on s'interroge, pas la position de l'utilisateur : parcelle cadastrale, zone du plan local d'urbanisme (U, AU, A, N : constructible ou non), altitude du sol, prix médians des maisons, appartements et terrains vendus autour, et sur la voie demandée, depuis 5 ans (DVF), loyers d'annonce de la commune pour un logement type (carte des loyers de l'ANIL), part des logements et locaux de la commune éligibles à la fibre (Arcep), antennes mobiles (opérateurs, 2G à 5G) et émetteurs de radio et de télévision à moins de 500 m (ANFR), et risques : plan de prévention des risques (PPR inondation, mouvements de terrain, littoral) au point, arrêtés de catastrophe naturelle de la commune, glissements et éboulements recensés à moins de 500 m, sismicité, radon. Pour : « cette parcelle est constructible ? », « prix au m² des maisons à l'Hermitage ? », « quels risques à cette adresse ? ».

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": {
      "adresse": "<adresse>"
    },
    "name": "fiche_terrain"
  }
}

Input Schema

NameRequiredDescriptionDefault
adresseYesLe bien ou le lieu sur lequel on s'interroge, pas la position de l'utilisateur : adresse du bien (« 7 rue de la Buse, Saint-Paul ») ou lieu-dit (« Bois de Nèfles »).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / adresse / description
      Previous value: -"Adresse (« 7 rue de la Buse, Saint-Paul »), lieu-dit (« Bois de Nèfles ») ou coordonnées « -21.0, 55.27 »."New value: +"Le bien ou le lieu sur lequel on s'interroge, pas la position de l'utilisateur : adresse du bien (« 7 rue de la Buse, Saint-Paul ») ou lieu-dit (« Bois de Nèfles »)."
  2. Changed1 schema field changed
    • changedInput schema / properties / adresse / description
      Previous value: -"Adresse (« 7 rue de la Buse, Saint-Paul »), lieu-dit (« Bois de Nèfles ») ou coordonnées « -21.0, 55.27 ». / Address, place or 'lat, lon'."New value: +"Adresse (« 7 rue de la Buse, Saint-Paul »), lieu-dit (« Bois de Nèfles ») ou coordonnées « -21.0, 55.27 »."
  3. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  4. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real behavioral context beyond that – the data comes from official registries, price lookback is 5 years, proximity-based items use a 500 m radius, and results are keyed to a property/place rather than the caller's position. It does not discuss output shape, multi-source latency, or what happens when a parcel has no PLU/PPR record, which keeps it from a 5.

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?

Purpose and the address caveat are front-loaded in the opening clause, followed by a dense but useful inventory of data sources and then example phrasings. The long enumeration makes it a run-on sentence, but nearly every listed item earns its place by telling the agent which questions this tool can answer.

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?

There is no output schema, so the description must convey the return contents – and it does so exhaustively, item by item with source names. Combined with a single fully documented parameter and read-only annotations, nothing an agent needs in order to call this correctly is missing.

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% and there is only one parameter, so the schema already carries the semantics; baseline is 3. The description does reinforce the one genuinely ambiguous point – the address is the property's location, not the user's position – which mirrors and strengthens the schema text, but adds no new format or disambiguation detail beyond it.

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 enumerates exactly what the tool returns – parcelle cadastrale, PLU zone (U/AU/A/N), sol altitude, DVF median prices over 5 years, ANIL rents, Arcep fiber share, ANFR antennas/transmitters within 500 m, and risks (PPR, arrêtés catastrophe naturelle, glissements, sismicité, radon). This is far more specific than a verb+resource label and leaves no doubt about what the tool does. It is also unmistakably distinct from every sibling (weather, water, transport, sports), none of which touch cadastre or urbanism.

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?

It closes with concrete trigger questions («cette parcelle est constructible ?», «prix au m² des maisons à l'Hermitage ?», «quels risques à cette adresse ?»), which tells the agent precisely what class of user request should route here. There are no exclusions or named alternatives, but no sibling overlaps this domain, so the omission is minor.

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

All rundata.re · La Réunion en direct 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