Skip to main content
Glama

get_water_level

Read-onlyIdempotent

Retrieve current river or lake water level and temperature for a Swiss BAFU hydro station by providing its station ID.

Instructions

Current river/lake level and temperature at a BAFU hydro station

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "station": "<station>"
    },
    "name": "get_water_level"
  }
}

Input Schema

NameRequiredDescriptionDefault
stationYesHydro station ID, e.g. 2135 (Aare/Bern), 2243 (Rhine/Basel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / station / description
      Previous value: -"Hydro station ID (e.g. 2135 for Aare/Bern, 2243 for Rhine/Basel)"New value: +"Hydro station ID, e.g. 2135 (Aare/Bern), 2243 (Rhine/Basel)"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so safety is covered. The description adds the returned measurement types, but omits units, freshness guarantees, and what happens with an invalid station.

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 a single front-loaded sentence with no wasted wording. It states the data returned and the source context directly.

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 simple one-parameter read-only tool with full schema coverage and annotations, the description is nearly complete. Minor gaps around units and temporal freshness remain but are not critical for selecting the 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 description coverage is 100%, and the schema already explains the station ID with examples. The description adds no additional meaning about the station parameter beyond what the schema provides, so baseline 3 is appropriate.

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 states a specific resource and measurement: current river/lake level and temperature at a BAFU hydro station. The word 'current' implicitly distinguishes it from get_water_history, but it does not explicitly name or contrast with that sibling.

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 'Current' versus the sibling get_water_history, but the description does not explicitly say when to use this tool instead of list_hydro_stations or get_water_history. No exclusions or prerequisites are stated.

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