rundata.re · La Réunion en direct

Sécheresse : restrictions d'eau à La Réunion

restrictions_eau

Read-only

Restrictions d'eau en cas de sécheresse à La Réunion (974), d'après l'arrêté préfectoral en vigueur (VigiEau) : niveau par commune (vigilance, alerte, alerte renforcée, crise) et ce qui est interdit (arrosage, lavage de voiture, piscine…) pour un particulier, une entreprise, une collectivité ou une exploitation agricole. Pour : « restrictions d'eau à Saint-Joseph ? », « j'ai le droit d'arroser mon jardin au Port ? », « je peux remplir ma piscine ? ». Sans lieu : toute l'île.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "restrictions_eau"
  }
}

Input Schema

Name	Required	Description	Default
`lieu`	No	Lieu à La Réunion : commune, plage, quartier, cirque, sommet, ou coordonnées « -21.05, 55.22 ». Vide = toute l'île.
`profil`	No	Pour qui (« exploitation » = agriculteur) ; par défaut un particulier.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / lieu / description

Previous value: -"Lieu à La Réunion, en texte libre : commune (« Saint-Paul »), plage (« plage de l'Hermitage », « Boucan Canot »), quartier, cirque (« Cilaos », « Mafate »), sommet (« Maïdo », « volcan »), ou coordonnées « -21.05, 55.22 ». Vide = tour de l'île. / Place in Réunion, free text or 'lat, lon'; empty = whole island."New value: +"Lieu à La Réunion : commune, plage, quartier, cirque, sommet, ou coordonnées « -21.05, 55.22 ». Vide = toute l'île."

changedInput schema / properties / profil / description

Previous value: -"Pour qui (« exploitation » = agriculteur) ; par défaut un particulier. / Who asks; default a private person."New value: +"Pour qui (« exploitation » = agriculteur) ; par défaut un particulier."

Changed1 schema field changedOct 26, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```

Changed1 schema field changedOct 25, 2026

changedInput schema / properties / profil / description

Previous value: -"Pour qui (« exploitation » = agriculteur) ; par défaut un particulier. / Who asks; default a private person."New value: +"Pour qui (« exploitation » = agriculteur) ; par défaut un particulier. / Who asks; default a private person."

AddedOct 24, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description still adds real value: the source of truth (arrêté préfectoral en vigueur, VigiEau), the granularity of the answer (level per commune), the categories covered, and the default island-wide behaviour when no location is given.

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 the resource and source, then the returned content, then user-style example queries, then the no-location default. Dense but every segment carries information; only minor redundancy between the body and the example phrasings.

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?

With no output schema, the description must convey the shape of the answer, and it does (restriction level per commune plus explicit prohibitions such as arrosage, lavage de voiture, piscine). Both optional parameters and their defaults are covered, so an agent can call it correctly with or without arguments.

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%, with both `lieu` (commune, plage, quartier, cirque, sommet, or "-21.05, 55.22" coordinates) and `profil` (enum with "exploitation" = agriculteur) already documented. The description restates the empty-location default and the actor profiles but adds no new syntax or constraints beyond the schema, so baseline 3 applies.

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 resource and scope: drought water restrictions in Réunion (974), per the arrêté préfectoral / VigiEau, returning a level per commune (vigilance, alerte, alerte renforcée, crise) plus what is prohibited. This is clearly distinguishable from siblings such as coupures_eau (outages) or vigilance_meteo (weather warnings).

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?

Three concrete example questions ("restrictions d'eau à Saint-Joseph ?", "j'ai le droit d'arroser mon jardin au Port ?", "je peux remplir ma piscine ?") tell the agent exactly what kind of user intent should route here, and "Sans lieu : toute l'île" defines the no-argument case. It stops short of naming an alternative tool for adjacent questions (e.g. coupures d'eau).

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 tools Inspect

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.