SiteCheck Trade & Energy

Current water level and discharge for one German federal

logistics_rhine_river_water_levels

Read-only

Current water level (W, cm) and discharge (Q, m3/s) for one German federal waterway gauge from PEGELONLINE (WSV), with the reading timestamp. Default station is KAUB (Middle Rhine, a key barge bottleneck). Barging capacity is not calculated; this is gauge data only. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "logistics_rhine_river_water_levels"
  }
}

Input Schema

Name	Required	Description	Default
`station`	No	PEGELONLINE station short name, e.g. KAUB, EMMERICH, COLOGNE (default KAUB)

Output Schema

Name	Required	Description	Default
`source`	No
`station`	No
`checkedAt`	No
`discharge`	No
`waterLevel`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds notable behavioral context the annotations don't carry: a per-successful-call price of $0.002 in USDC via x402 (Base, Solana or Arc) and the guarantee that failed calls are not charged. It doesn't discuss rate limits or data freshness/refresh cadence, keeping it from a 5.

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 sentences, each earning its place: data content and units first, source second, default and its relevance third, scope limit and pricing last. Front-loaded and free of redundant restatement of the title.

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

Completeness5/5

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

An output schema exists, so return values need not be spelled out. The description covers data content, units, source, default parameter behavior, scope limitation, and cost/payment mechanics — everything an agent needs to decide and invoke correctly for a single-parameter read tool.

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 coverage is 100% and the single parameter already documents the station short name and default. The description adds a little context by explaining why KAUB is the default (barge bottleneck), but no additional syntax or format guidance. Baseline 3 is appropriate given the schema does the heavy lifting.

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 states a specific verb and resource (current water level W in cm and discharge Q in m3/s for one German federal waterway gauge) with the data source (PEGELONLINE/WSV). Units and the timestamp inclusion make the output unambiguous. It is clearly distinguishable from siblings like logistics_mississippi_barge_rates.

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?

It gives clear context: default station KAUB on the Middle Rhine, described as a key barge bottleneck, and explicitly states 'Barging capacity is not calculated; this is gauge data only', which steers an agent away from using it for capacity questions. It lacks an explicit pointer to an alternative tool, so it stops short of a 5.

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

All SiteCheck Trade & Energy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?