Skip to main content
Glama
Sign In
rundata-re

rundata · La Réunion 974 en direct

by rundata-re
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Crues et rivières à La Réunion

crues_rivieres
Read-onlyIdempotent

Check Réunion river flood vigilance and live water levels or flow at 29 stations, with trends and historical flood markers, to assess whether a river or ravine is rising.

Instructions

Vigilance crues de Vigicrues Réunion (DEAL), rivière par rivière, et hauteur d'eau et débit mesurés toutes les 5 minutes aux 29 stations des rivières et ravines de l'île, avec leur tendance et les crues historiques comme repères. Rappeler de ne jamais traverser un radier submergé. Pour : « la rivière des Galets est en crue ? », « il y a une vigilance crues ? », « niveau de la ravine Saint-Gilles ? ».

Input Schema

NameRequiredDescriptionDefault
lieuNoUne rivière (« rivière des Galets », « ravine Saint-Gilles ») ou un lieu (« Salazie », « Saint-Benoît ») pour les stations proches. Vide = toute l'île.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.203.95
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / lieu / description
      Previous value: -"Une rivière (« rivière des Galets », « ravine Saint-Gilles ») ou un lieu (« Salazie », « Saint-Benoît ») pour les stations proches. Vide = toute l'île. / A river or a place; empty = whole island."New value: +"Une rivière (« rivière des Galets », « ravine Saint-Gilles ») ou un lieu (« Salazie », « Saint-Benoît ») pour les stations proches. Vide = toute l'île."
  2. Addedv0.128.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations confirm it is a read-only, non-destructive tool. The description adds valuable behavioral context by stating that measurements are taken 'toutes les 5 minutes' and include 'crues historiques'. While it adds data context, it doesn't add significant operational/safety info beyond what's already structurally available, hence a solid middle score.

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 text is dense but highly informative. It front-loads the core functionality and then provides examples, maintaining a good balance between detail and readability without unnecessary jargon.

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?

The combination of the description, title, and the single parameter's clear function makes the tool definition complete. Given the 'readOnlyHint' and the specific example queries, the AI has everything it needs to select and invoke the tool confidently.

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?

The schema coverage is 100%, meaning the description doesn't need to add basic parameter definitions. However, the description adds significant semantic meaning by defining exactly what constitutes a valid 'lieu' (e.g., 'une rivière... ou un lieu... pour les stations proches'), which goes beyond a simple string type.

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 title 'Crues et rivières à La Réunion' combined with the description clearly states the tool provides real-time flood monitoring ('Vigilance crues'). It specifies the resource (river/ravine data) and the scope (the island of Réunion), making its purpose highly specific and easy to distinguish from sibling tools like 'meteo_actuelle' or 'volcan_seismes'.

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?

The description explicitly provides three example query patterns ('la rivière des Galets est en crue?', etc.). This gives the AI clear guidance on the intent and phrasing required, effectively serving as 'when to use' examples compared to other situational tools.

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