Skip to main content
Glama
schlpbch

Aareguru MCP Server

by schlpbch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Aare Map

aare_map

Display an interactive map of Aare monitoring stations with color-coded safety levels. Select any marker to view water temperature, flow, and Swiss German details.

Instructions

Show an interactive OpenStreetMap with all Aare monitoring stations.

Each city is plotted as a circle marker coloured by BAFU safety level. Click a marker to see temperature, flow, and Swiss German description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoOptional city identifier to fly to on load (e.g. 'Bern', 'Thun'). Omit to show all cities with the map fitted to bounds.
langNode

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.9.0
    • addedInput schema / properties / lang
      Added value: +{
+  "default": "de",
+  "type": "string"
+}
  2. Addedv4.6.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries full behavioral burden. It discloses that the tool is interactive, that markers are colored by BAFU safety level, and that clicking reveals temperature, flow, and Swiss German description. It does not mention side effects, data source freshness, or error behavior, but for a display tool this is substantial behavioral disclosure.

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 compact and front-loaded with the primary purpose. Each subsequent line adds concrete behavioral detail, and there is no filler or repetition of schema information beyond what is necessary.

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

Completeness3/5

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

For a simple display tool the description covers the main interactions and map content, but it omits lang parameter semantics, any error or error-handling behavior, and does not clarify the refresh data source. These gaps leave the agent without full guidance for edge cases like invalid city values or non-German language requests.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, with the lang parameter lacking any description. The tool description does not compensate by explaining language values or how lang affects labels/descriptions. It only restates what the schema already says about city, and leaves the lang parameter under-specified for the agent.

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 uses a specific verb and resource ('Show an interactive OpenStreetMap with all Aare monitoring stations') and adds concrete detail about marker colors and click behavior. It clearly differentiates itself from sibling view tools like forecast_view or compare_cities by focusing on the map display of monitoring stations.

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

Usage Guidelines3/5

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

The description implies usage for displaying station information on a map, and the schema explains the city optionality, but it does not explicitly state when to prefer this tool over refresh_map or other station-based views. No exclusions or alternative routing are provided, so usage context is only implied.

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

Deploy Server

Other Tools