Aare.guru MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_citiesB | Get list of all available cities/locations with Aare data |
| get_current_conditionsA | Get comprehensive current Aare data for a specific location including temperature, flow, forecasts |
| get_today_summaryB | Get minimal current Aare temperature and swimming recommendation for a location |
| get_widget_dataA | Get current Aare data for all locations at once, suitable for widgets/dashboards |
| get_historical_dataB | Get historical time series data for water temperature, flow, and air temperature |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Tools are largely distinct: get_cities lists locations, get_current_conditions provides comprehensive data for one location, get_today_summary offers a minimal subset (temp + swim recommendation), get_historical_data gives time series, and get_widget_data aggregates current data for all locations. Slight overlap between current conditions and today summary, but descriptions clarify the difference.
All tool names consistently use the get_ prefix with snake_case and follow a clear verb_noun pattern (e.g., get_cities, get_current_conditions). The naming is uniform and predictable.
With 5 tools covering city listing, two levels of current data, historical data, and aggregated data, the set is well-scoped for the domain of Aare river data access. The number is appropriate and not excessive.
The tool set provides complete coverage for a read-only data API: city enumeration, current conditions (both comprehensive and minimal), historical time series, and batch data for dashboards. There are no obvious gaps, as the domain does not require create, update, or delete operations.