Skip to main content
Glama
schlpbch

Aareguru MCP Server

by schlpbch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Safety Briefing

safety_briefing

Check the official BAFU 1–5 danger scale for the Aare river and get plain-language swimming guidance based on the current flow danger level for your chosen city.

Instructions

Show the official BAFU 1–5 danger level scale with the current reading highlighted.

Translates the hydrological danger level into plain swimmer guidance, using the actual flow_gefahrenstufe from the API where available.

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

B3.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 burden of behavioral disclosure. It does explain the main behavior: displaying a scale, highlighting the current reading, and translating danger levels into guidance. However, it does not clarify fallback behavior when API data is unavailable, whether the tool is read-only, or what exact output format the agent should expect.

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 two focused sentences with the core purpose front-loaded. The second sentence adds valuable context about translating the danger level into plain swimmer guidance without unnecessary detail.

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?

The tool is relatively simple with two optional parameters and no output schema, so the description is mostly adequate. Still, it lacks important context about the output format, accepted language values, and behavior when the flow_gefahrenstufe is unavailable.

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 description coverage is only 50%, and the description adds no parameter-level meaning. The 'city' parameter is documented in the schema, but 'lang' has only a default with no explanation, and the description does not clarify how either parameter affects the safety briefing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: showing the official BAFU 1–5 danger level scale with the current reading highlighted and translating it into swimmer guidance. This differentiates it from raw-data siblings like get_flow_danger_level, but it does not explicitly name any sibling alternatives.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is provided. The description does not mention alternatives or conditions for choosing this tool over related tools such as flow_card or get_flow_danger_level.

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