Skip to main content
Glama
bLd75

rundata · La Réunion 974 en direct

by bLd75
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

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

restrictions_eau
Read-onlyIdempotent

Check drought water restrictions in Réunion by commune and user profile, including prohibited uses like watering, car washing, and pools.

Instructions

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) pour l'eau du robinet, les rivières et sources, les nappes, 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. / Drought water-use restrictions in Réunion Island, per commune.

Input Schema

NameRequiredDescriptionDefault
lieuNoLieu à 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.
profilNoPour qui (« exploitation » = agriculteur) ; par défaut un particulier. / Who asks; default a private person.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.128.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, so safety is covered. The description adds valuable context beyond that: the authoritative source (préfectoral decree / VigiEau), the four severity levels, and the default profile applied when unspecified.

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?

Information-dense and front-loaded: what it is, what it returns, when to ask, then the defaults. The bilingual duplication is somewhat verbose, but each sentence carries content rather than filler.

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 zero-required-parameter, read-only lookup with no output schema, the description covers source, granularity (commune), levels, activities covered, and profiles. Only an indication of how results are structured (per-commune list vs. single verdict) is left implicit.

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; the description nevertheless reinforces the semantics of both parameters by showing real-world query shapes and stating that an empty lieu means an island-wide tour and an unspecified profil defaults to a private individual.

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+resource: drought water-use restriction levels per commune in Réunion, with the source (arrêté préfectoral / VigiEau) and the covered domains (tap water, rivers, groundwater). This clearly separates it from siblings like coupures_eau (outages) or qualite_eau (water quality).

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?

Gives concrete triggering questions (« restrictions d'eau à Saint-Joseph ? », « je peux remplir ma piscine ? ») and states the default when no location is given (whole island). It does not explicitly exclude neighbouring tools such as coupures_eau or vigilance_meteo, but the usage context is unambiguous.

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

Deploy Server

Other Tools