Skip to main content
Glama
schlpbch

Aareguru MCP Server

by schlpbch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Conditions Dashboard

conditions_dashboard

Displays an interactive dashboard of current Aare river conditions, including water temperature, flow rate, safety level, and danger alerts for a selected city.

Instructions

Show an interactive aare.guru-style dashboard of current Aare conditions.

Displays water temperature in the signature Aare cyan (#2be6ff) card, flow rate, BAFU safety level with the characteristic thick teal border, Swiss German description, and a danger alert when flow is elevated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity identifier (e.g. 'Bern', 'Thun', 'Olten')Bern
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 provided, the description carries the burden of explaining behavior. It does so by describing the interactive UI, the signature visual styling, and the danger alert triggered by elevated flow, which tells the agent what output to expect. It does not cover data freshness or side effects, but 'Show' plus the UI details makes its read-only nature reasonably clear.

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 with no filler; the first sentence states the core purpose and the second packs the distinguishing visual details. Details like #2be6ff and the thick teal border are purposeful for identifying the expected output style rather than decorative.

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 visual view tool with no output schema, the description covers the main rendered elements and the alert condition, which is most of what an agent needs to decide to call it. It is incomplete on how city and lang influence the output, and it does not mention sibling tools by name for routing.

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% and the description adds no parameter-level meaning: it never mentions how 'city' selects the river section or how 'lang' affects the Swiss German description. The lang parameter has no schema description, and the description does not compensate for that gap.

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 opens with a specific verb and resource: 'Show an interactive aare.guru-style dashboard of current Aare conditions.' It then enumerates the dashboard's contents (temperature, flow, BAFU safety level, Swiss German description, danger alert), which clearly distinguishes it from sibling single-value cards like get_current_temperature or get_current_conditions.

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 phrase 'dashboard of current Aare conditions' implies this is the composite view tool, distinct from forecast or historical tools, but the description never gives explicit when-to-use or when-not-to-use guidance. There are no named alternatives or exclusions, so an agent must infer routing from sibling names.

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