Skip to main content
Glama

Rhine water level: Maxau, Kaub, Köln, Duisburg-Ruhrort, Emmerich (PEGELONLINE)

get_rhine_water_level
Read-only

Free. Current Rhine water level in cm at the gauges Maxau, Kaub, Köln, Duisburg-Ruhrort and Emmerich from PEGELONLINE (WSV open data), with the trend and level class as published by WSV and water temperature where the station measures it. Kaub is the usual low-water reference for shipping. Not a forecast and not a flood warning; a station with ok=false had no reading. Refreshed every 5 minutes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_rhine_water_level"
  }
}

Input Schema

NameRequiredDescriptionDefault
stationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only cover readOnlyHint and openWorldHint, and the description adds genuinely useful context beyond them: freshness ('Refreshed every 5 minutes'), a documented failure mode ('a station with ok=false had no reading'), conditional field presence ('water temperature where the station measures it'), and the no-cost/open-data provenance. Missing any note on rate limits or whether 'all' aggregates or errors, but the operational picture is strong.

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?

Four dense sentences, front-loaded with the value proposition, then the reference-station hint, then the exclusions, then freshness. No filler; every clause conveys something an agent would act on.

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?

With no output schema, the description does the work of describing the return payload (level in cm, trend, level class, temperature, ok flag), which is exactly what's needed. The residual gap is the undocumented 'all' selector and default behavior when station is omitted.

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 0%, so the description carries the burden. It maps the human gauge names (Maxau, Kaub, Köln, Duisburg-Ruhrort, Emmerich) onto the enum values, which helps, but never mentions the 'all' option or what happens when the parameter is omitted (required=0). Partial compensation only.

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?

States a specific verb and resource (current Rhine water level in cm), names all five gauges, names the upstream data source (PEGELONLINE/WSV), and lists the payload fields (trend, level class, water temperature). An agent knows exactly what this returns without opening anything else.

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?

Provides real scoping guidance: 'Kaub is the usual low-water reference for shipping' tells the agent which station matters for the common use case, and 'Not a forecast and not a flood warning' explicitly excludes adjacent use cases. It stops short of naming a concrete alternative tool, so it lands at 4 rather than 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.