Aareguru MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Current Conditions

get_current_conditions

Retrieve complete current Aare river conditions for a city, enabling swim safety assessments and answering 'Is it safe to swim?' using official BAFU thresholds.

Instructions

Get complete current conditions for a city.

Use this for safety assessments, 'is it safe to swim?' questions, and when users need a complete picture before swimming. This is the most detailed tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No	City identifier (e.g., 'Bern', 'Thun', 'Olten'). Use `list_cities()` to discover available locations.	Bern

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv4.6.0May 10, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / city / description

Added value: +"City identifier (e.g., 'Bern', 'Thun', 'Olten').\n  Use `list_cities()` to discover available locations."

removedOutput schema / $defs

Removed value: -{
-  "AareConditionsData": {
-    "description": "Aare conditions data for conditions tool response.",
-    "properties": {
-      "flow": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Flow rate in m³/s"
-      },
-      "flow_text": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Flow description"
-      },
-      "forecast2h": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Temperature forecast for 2 hours"
-      },
-      "forecast2h_text": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Forecast description"
-      },
-      "height": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Water height in meters"
-      },
-      "location": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Location name"
-      },
-      "location_long": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Full location name"
-      },
-      "swiss_german_explanation": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "English translation"
-      },
-      "temperature": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Water temperature in Celsius"
-      },
-      "temperature_text": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Swiss German temperature description"
-      },
-      "temperature_text_short": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Short description"
-      },
-      "warning": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Safety warning if applicable"
-      }
-    },
-    "type": "object"
-  }
-}

addedOutput schema / additionalProperties
```
Added value: +true
```

removedOutput schema / description

Removed value: -"Response model for get_current_conditions tool."

removedOutput schema / properties

Removed value: -{
-  "aare": {
-    "anyOf": [
-      {
-        "$ref": "#/$defs/AareConditionsData"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Aare river data"
-  },
-  "city": {
-    "description": "City identifier",
-    "type": "string"
-  },
-  "forecast": {
-    "anyOf": [
-      {
-        "items": {
-          "additionalProperties": true,
-          "type": "object"
-        },
-        "type": "array"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Weather forecast"
-  },
-  "seasonal_advice": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Season-specific guidance"
-  },
-  "weather": {
-    "anyOf": [
-      {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Current weather conditions"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "city"
-]
```

First observedv3.3.0Feb 8, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description bears the transparency burden. It indicates the tool returns complete current conditions and is the most detailed option, but it does not disclose specifics like data sources, potential failure modes, or that it is read-only. The 'get' prefix implies read-only behavior, so this is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with no fluff. Purpose is front-loaded, usage guidance follows, and the 'most detailed tool' claim reinforces selection without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with an output schema, the description is complete enough. It gives clear use cases and the schema handles parameter and return details. It could mention that the city defaults to Bern, but the schema already covers that, so no significant gap exists.

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 description coverage is 100%, and the schema already provides a clear explanation of the 'city' parameter, including examples and a pointer to list_cities(). The tool description adds no additional parameter meaning, so the baseline score of 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?

The description states a specific verb and resource: 'Get complete current conditions for a city.' It explicitly distinguishes itself from siblings by calling itself 'the most detailed tool,' separating it from get_current_temperature and get_flow_danger_level.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states when to use the tool: 'for safety assessments, 'is it safe to swim?' questions, and when users need a complete picture before swimming.' It does not mention exclusions or alternatives, but the context is sufficiently clear for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.