Skip to main content
Glama
schlpbch

Aareguru MCP Server

by schlpbch

Related Servers

Alternatives to Aareguru MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides access to real-time and historical water conditions of the Aare river in Switzerland, including water temperature, flow rates, swimming recommendations, and data from multiple monitoring locations along the river.
      5
      6 npm
      1
      GPL 3.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI models to access Swiss weather and climate data from MeteoSwiss, including current observations, forecasts, and warnings.
      6
      68 PyPI
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Connects AI assistants to Swiss environmental data from BAFU, including air quality, hydrology, natural hazards, and open datasets, with no API keys required.
      21
      84 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to look up official Austrian municipal data by place name, GKZ or coordinates, returning weather forecasts and nowcasts from GeoSphere Austria alongside nearby and current water-level readings from eHYD. Answers come as compact JSON with source attribution, timestamps, licenses and units, plus tools for searching municipalities and checking flood situations by province.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides access to official MeteoSwiss weather data, including regional reports, daily forecasts, and website search functionality across multiple languages. It enables AI assistants to retrieve real-time weather information and documentation from MeteoSwiss using the Model Context Protocol.
      3
      Creative Commons Zero v1.0 Universal

    TDQS

    C2.9/5.0

    Scored across 42 tools

    Disambiguation2/5

    Many tools have overlapping purposes: get_current_temperature/temperature_card/conditions_dashboard all report current conditions, compare_cities/compare_cities_table/fetch_comparison overlap, and the 13 refresh_* tools are nearly identical except for the resource name. UI view tools and data retrieval tools form unclear boundaries for an agent deciding which tool to call.

    Naming Consistency2/5

    Naming is inconsistent across the set: get_current_temperature and compare_cities use verb_noun, shop_cart_view and weather_card use noun_view/noun_card, while refresh_shop_cart, fetch_history, and forecast_view mix different verb prefixes. The patterns are individually readable but do not form one predictable convention.

    Tool Count2/5

    42 tools is excessive for the apparent scope of river conditions plus a small merchandise shop. Many tools are UI-only views and refresh actions that duplicate the same underlying data operations, inflating the surface without adding meaningful agent capabilities.

    Completeness4/5

    The core domain is well covered: current conditions, forecasts, historical data, comparisons, safety levels, and the full checkout lifecycle from listing products to payment URL. Minor gaps exist, such as no dedicated sun data retrieval separate from the sun_card view, but agents can accomplish the main workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues