Skip to main content
Glama

Historical water data for a station

get_water_history
Read-only

Fetch historical water level, discharge, or temperature for a FOEN station over a date range to compare recent hydrological conditions.

Instructions

Historical water level, discharge or temperature for a FOEN station over a date range (recent weeks). Get the station ID from list_hydro_stations. Long ranges are downsampled to bucket means (with min/max) to stay compact.

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>",
      "date_from": "<date_from>"
    },
    "name": "get_water_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_toNoEnd date (default: today)
date_fromYesStart date YYYY-MM-DD
parameterNoflow
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 safety is covered. The description does add real behavioral context — long ranges are downsampled to bucket means with min/max, and the effective window is 'recent weeks' — which an agent must know to interpret results. However it doesn't cover failure modes (unknown station ID, out-of-range dates) or rate/response size limits beyond the compaction note.

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?

Three short sentences, front-loaded with the core purpose, then the prerequisite, then the one non-obvious behavior. Nothing is redundant and no sentence could be dropped 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?

No output schema exists, and the definition partially compensates by explaining that results are bucket means with min/max, so the agent knows what the returned values represent. With 4 parameters and 75% schema coverage the gaps are small; a note on the default 'today' end date or invalid-station behavior would make it 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 coverage is 75%, so most parameters are already documented. The description usefully maps the prose terms 'water level, discharge or temperature' onto the height/flow/temperature enum and reinforces station_id provenance and the date-range meaning. That is confirmation rather than new semantics, so it sits at the baseline-plus level.

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?

States a specific verb (get historical) plus the resource (water level, discharge or temperature) and scope (FOEN station, date range). It implicitly separates itself from current-value siblings like get_water_data/get_current_measurements via the word 'Historical', but never names those alternatives, so the differentiation is inferential rather than explicit.

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?

Gives a concrete prerequisite workflow: 'Get the station ID from list_hydro_stations', which is exactly the step an agent needs before calling. It also flags the practical bound ('recent weeks'). It stops short of saying when to prefer this over get_water_data or what to do if a requested range falls outside the supported window.

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