Aareguru MCP Server

get_current_conditions

Retrieve complete current conditions for a Swiss Aare river city to assess swimming safety and water quality.

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. Dates show when Glama detected each change.

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

A3.8/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It states 'complete current conditions' but does not disclose whether the tool is read-only, requires authentication, or has any side effects. No mention of data freshness, pagination, or response structure.

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?

Two sentences, no fluff. Purpose and usage guidelines are front-loaded. Every sentence adds value.

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 simple 1-parameter tool with an output schema, the description is mostly sufficient. It names the resource and usage context. Could briefly explain what 'complete' covers, but output schema likely handles that.

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 already has 100% coverage with a description for the 'city' parameter including examples and a reference to list_cities(). The tool description adds no extra parameter semantics beyond what is in the schema, so baseline 3 is appropriate.

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?

Description clearly states 'Get complete current conditions for a city', uses a specific verb and resource. It differentiates from siblings by claiming 'This is the most detailed tool' and provides concrete usage examples such as safety assessments and swimming questions.

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 tells when to use: 'Use this for safety assessments, is it safe to swim? questions, and when users need a complete picture before swimming.' It implies this is the most detailed option but does not explicitly state when to avoid it or mention alternatives like get_current_temperature.

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

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/schlpbch/aareguru-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server