Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_river_gauge_level

Get live river water levels (cm), 24h delta, and flood/navigation trend from WSV Pegelonline (Rhine, Elbe, Danube, Main, Moselle, Weser).

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_river_gauge_level"
  }
}

Input Schema

NameRequiredDescriptionDefault
stationNoStation or city (e.g. Köln, Düsseldorf, Kaub, Dresden, Passau, Frankfurt)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the authoritative upstream source (WSV Pegelonline), freshness ("live"), units (cm), the derived fields returned (24h delta, flood/navigation trend), and geographic scope. It omits edge behavior such as fallback when the station is unknown or ambiguous, and whether a station list can be discovered.

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?

One densely packed sentence with zero filler; what the tool returns is front-loaded and the source, units, and coverage trail behind as supporting detail. Nothing could be removed without losing information.

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 one-parameter read tool with no output schema, the description covers source, units, returned fields, and coverage, which is nearly everything an agent needs. The remaining gap is behavior with an empty or unresolvable station argument.

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 100% and the single parameter already documents that it accepts a station or city with examples, so the description need not restate it. However, the parameter is not required and the description never explains what happens when it is omitted (all stations? a default gauge?), which is the one meaningful parameter question left open.

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?

Specific verb ("Get") plus resource ("live river water levels") with concrete returned fields (cm, 24h delta, flood/navigation trend) and named data source (WSV Pegelonline) and coverage rivers. An agent knows exactly what this returns, and no sibling tool in the list overlaps with hydrology data.

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?

Usage is implied by the narrow subject matter (live river levels) and the request-like examples of stations/cities, but there is no explicit when-to-use framing, no stated exclusions, and no guidance on what to do when no relevant station is known. Adequate for a single-purpose tool but not instructive.

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.

Resources