No user-submitted related servers found.
Scored across 3 tools
The tools have overlapping purposes that could cause confusion. v2_2 and v2_3 both get current weather data, differing only by input method (latitude/longitude vs. city name), which may lead to misselection. v2 provides forecast data, which is distinct, but the two current weather tools are ambiguous in scope.
The naming is inconsistent and lacks a clear pattern. Tools are named v2, v2_2, and v2_3, which are opaque and do not follow a verb_noun convention. This makes it hard to infer functionality from names alone, though the descriptions provide clarity.
With 3 tools, the count is borderline but reasonable for a weather API server. It covers current weather and forecast data, but the scope feels thin, as it lacks tools for other common weather operations like historical data or alerts, making it slightly under-scoped.
There are significant gaps in the tool surface for a weather domain. It only provides current weather (with two similar tools) and a 5-day forecast, missing operations like historical weather, air quality, alerts, or multi-location queries. This incompleteness could cause agent failures for broader weather-related tasks.