Skip to main content
Glama

Live water data for a station

get_water_data
Read-only

Retrieves current water level, discharge, and temperature for a Swiss FOEN hydrology station by numeric ID; first find the station ID with list_hydro_stations.

Instructions

Latest water level, discharge and temperature for a FOEN hydrology station, by numeric station ID. Do not guess IDs: call list_hydro_stations with a river, lake or place name first and use the station_id it returns.

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_id": "<station_id>"
    },
    "name": "get_water_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
station_idYesFOEN station number as returned by list_hydro_stations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-source profile is covered. The description adds that values are current rather than archived, but says nothing about freshness/latency, units, missing measurements, or rate limits — meaningful gaps for a live external feed that the annotations cannot express.

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?

Two sentences, zero filler: the capability and its outputs come first, and the ID-provenance constraint follows immediately. 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 single-parameter, read-only lookup with no output schema, the definition covers what is returned (level, discharge, temperature), how to obtain the key input, and the read-only nature. A brief note on units or data latency would make it fully complete.

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 states the station number is "as returned by list_hydro_stations" with a numeric pattern. The description's parameter guidance therefore largely restates structured data, though the emphatic "do not guess" framing adds a little operational value. Baseline 3 applies.

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 verb and resource ("Latest water level, discharge and temperature for a FOEN hydrology station") and scopes it to a single station by numeric ID. The word "Latest" implicitly distinguishes it from a history sibling, but that sibling (get_water_history) is never named, so the differentiation is only implied.

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 an explicit negative instruction ("Do not guess IDs") plus the concrete alternative workflow: call list_hydro_stations with a place name first and use the returned station_id. That is strong when-to-use and prerequisite guidance; it stops short of a 5 because it doesn't cover the historical-data alternative or what to do if a station lacks a measurement.

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