Skip to main content
Glama

get_water_history

Read-onlyIdempotent

Retrieve historical river and lake levels for a Swiss BAFU hydro station within the last 32 days, using a date range and optional resolution.

Instructions

Historical river/lake levels for a BAFU hydro station. Only the last 32 days are available

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

Input Schema

NameRequiredDescriptionDefault
stationYesHydro station ID
end_dateYesYYYY-MM-DD
resolutionNoauto summarises long ranges to min/max/mean per periodauto
start_dateYesYYYY-MM-DD, within the last 32 days

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.0
    • changedInput schema / properties / end_date / description
      Previous value: -"End date YYYY-MM-DD"New value: +"YYYY-MM-DD"
    • addedInput schema / properties / resolution
      Added value: +{
      +  "default": "auto",
      +  "description": "auto summarises long ranges to min/max/mean per period",
      +  "enum": [
      +    "auto",
      +    "raw",
      +    "hourly",
      +    "daily"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / start_date / description
      Previous value: -"Start date YYYY-MM-DD"New value: +"YYYY-MM-DD, within the last 32 days"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish this as a read-only, idempotent, non-destructive, open-world call, so the safety profile needs no repetition. The description adds genuine behavioral context on its own by disclosing the 32-day retention limit on historical data, though it says nothing about what happens for out-of-range dates or about units/aggregation in the returned series.

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 short sentences with zero filler: the resource is front-loaded and the availability caveat follows immediately. Nothing is repeated from the title or schema.

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 4-parameter read tool with full schema coverage, no output schema, and complete annotation coverage, the definition covers identity and the key hard limit. The only real gap is the shape of the returned time series (units, cadence), which an agent might reasonably want when choosing a resolution.

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%, including the enum values and the 'auto summarises long ranges to min/max/mean per period' note for resolution, so the schema carries the parameter burden. The description adds only the clarification that 'station' means a BAFU hydro station, which is marginal but useful.

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 ('Historical river/lake levels') and scopes it to 'a BAFU hydro station', which separates it from a generic weather or level tool. It does not explicitly name the current-reading sibling (get_water_level), so an agent must infer the historical-vs-current split from the wording alone.

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?

The 32-day availability window is a useful usage constraint that steers the agent away from long backfills, but there is no explicit guidance on when to pick this over get_water_level or get_weather_history, and no statement about prerequisites such as needing a station ID from list_hydro_stations.

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