Skip to main content
Glama
bLd75

rundata · La Réunion en direct

by bLd75
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Prévision météo à La Réunion

prevision_meteo
Read-onlyIdempotent

Get up to 7-day forecast data for Réunion Island places to answer questions about rain, temperatures, wind, and conditions by day and 3-hour periods.

Instructions

PRÉVISION météo (modèle numérique, pas une mesure) pour un lieu de La Réunion (974), de ce soir à 7 jours : ciel, températures min et max ramenées à l'altitude du lieu, pluie, vent et rafales, par jour et par tranches de 3 h. Pour toute question sur le temps à venir : « il va pleuvoir demain à Saint-Denis ? », « quel temps ce week-end à Cilaos ? », « il fera beau cet après-midi à l'Hermitage ? », « prévisions pour la Plaine des Cafres samedi ». Chaque réponse est étiquetée « prévision » avec ses limites (le modèle ne voit pas les microclimats de l'île) ; pour un cyclone, renvoie à la vigilance officielle de Météo-France. Pour le temps qu'il fait maintenant, utiliser meteo_actuelle. / Weather FORECAST (numerical model, not a measurement) for a place in Réunion Island, up to 7 days: 'will it rain tomorrow in Saint-Pierre?', 'weather this weekend in Cilaos?'. Always labelled as a forecast.

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.
quandNoQuand, en texte libre : « aujourd'hui », « cet après-midi », « ce soir », « cette nuit », « demain », « demain matin », « après-demain », un jour (« samedi »), « ce week-end », « dans 3 jours ». Vide = prochaines 24 h et jours suivants. / When, free text (today, tonight, tomorrow, a weekday, weekend); empty = next 24 h and following days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly/openWorld/idempotent), it discloses that output is probabilistic model data, that every answer is labelled 'prévision', that microclimates are not resolved, and that cyclone queries should be deflected to official vigilance. Those are exactly the caveats an agent needs to phrase results safely.

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 core distinction (forecast not measurement) and horizon, then examples, then limits and routing. The full bilingual duplication roughly doubles length and repeats example phrasings already present in the parameter schemas, which is mild waste but keeps both audiences served.

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?

With only two optional free-text parameters and no output schema, the description still specifies what variables come back, the granularity (per day and 3-hour blocks), the temporal horizon and the labelling/limitation caveats. Nothing an agent needs in order to call or present results 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 coverage is 100% and both parameters already document free-text place formats, coordinate syntax and empty-means-default behaviour. The description only implies the place must be in Réunion and the window is tonight-to-7-days, adding little beyond the schema. 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 the specific resource (weather forecast for a place in Réunion), the source (numerical model, not a measurement), the horizon (tonight to 7 days) and the returned variables (sky, min/max temperature adjusted to altitude, rain, wind, gusts, per day and 3-hour blocks). It explicitly contrasts itself with meteo_actuelle, so an agent can separate it from the sibling at a glance.

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?

Gives concrete trigger questions ('will it rain tomorrow in Saint-Denis?') and an explicit negative route: use meteo_actuelle for current conditions, and refer to Météo-France vigilance for cyclones. Both the when-to-use and the when-not-to-use cases are spelled out.

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