No user-submitted related servers found.
Scored across 17 tools
The provider-specific forecast tools (gfs_forecast, ecmwf_forecast, jma_forecast, dwd_icon_forecast, gem_forecast, metno_forecast, meteofrance_forecast) overlap heavily with the generic weather_forecast, which also returns model data. Descriptions clarify that provider tools are for multi-model comparison, but the boundary between picking weather_forecast and a specific provider tool is not always obvious. Other tools (air_quality, marine_weather, elevation, flood_forecast, geocoding) are clearly distinct.
Names are consistently lowercase snake_case, which is good, but the pattern is mixed: some use {provider}_forecast (gfs_forecast), others use bare domain nouns (air_quality, elevation, geocoding), and weather_forecast/weather_archive use a weather_ prefix. Still readable and mostly predictable.
17 tools is on the heavy side, and seven of them are near-duplicate provider-specific forecast endpoints that largely could have been a single parameterized forecast tool. The remaining domain tools (air quality, marine, flood, elevation, geocoding, archive, seasonal, climate) each earn their place.
Coverage is broad and complete for a weather API: current/forecast, ensemble, seasonal, climate projections, historical archive, air quality, marine, flood, and elevation. Minor gaps like no explicit 'current conditions' or station/observation tool, but core lifecycle is well covered.