Aareguru MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Flow Danger Level

get_flow_danger_level

Check real-time Aare river flow and BAFU danger rating to determine swimming safety. Use official thresholds to assess whether conditions are safe or hazardous.

Instructions

Get current flow rate and BAFU danger assessment.

Use this for safety-critical questions about current strength and swimming danger.

Flow Safety Thresholds:

<100 m³/s: Safe · 100-220: Moderate · 220-300: Elevated
300-430 m³/s: High — dangerous · >430: Very high — extremely dangerous

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.

Changed6 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."

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

removedOutput schema / description

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

removedOutput schema / properties

Removed value: -{
-  "city": {
-    "description": "City identifier",
-    "type": "string"
-  },
-  "danger_level": {
-    "anyOf": [
-      {
-        "type": "integer"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Numeric danger level (1-5)"
-  },
-  "flow": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Current flow rate in m³/s"
-  },
-  "flow_text": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Flow description"
-  },
-  "flow_threshold": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Danger threshold for this location"
-  },
-  "safety_assessment": {
-    "description": "Safety evaluation",
-    "type": "string"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "city",
-  "safety_assessment"
-]

First observedv3.3.0Feb 8, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses the output type and provides interpretable danger thresholds, but it does not mention data freshness, potential delays, failure behavior, or limitations of the BAFU assessment. That is a meaningful gap for a safety-critical tool.

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?

The description is front-loaded with purpose, then gives a clear use case and a compact threshold table. Every sentence earns its place and there is no filler.

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

Completeness5/5

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

For a one-optional-parameter tool with an output schema, the description provides purpose, usage context, and interpretive thresholds. The schema covers parameter discovery and defaults, so nothing essential is missing for correct invocation.

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 already documents the city parameter, default, and list_cities() discovery path. The description adds no additional parameter semantics, so the baseline 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 ('Get'), a clear resource ('current flow rate and BAFU danger assessment'), and immediately distinguishes itself from forecast, historical, temperature, and condition siblings. The safety context further clarifies its unique role.

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?

Explicitly says to use it for safety-critical questions about current strength and swimming danger. It does not name specific alternatives or state when not to use it, so it stops short of a 5.

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