Skip to main content
Glama

list_hydro_stations

Read-onlyIdempotent

Retrieve BAFU hydro station IDs for Swiss rivers and lakes so you can reference monitoring stations in queries and data workflows.

Instructions

List BAFU hydro station IDs (rivers, lakes)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds that the payload is station IDs rather than measurements and that both rivers and lakes are included, but says nothing about result size, ordering, or whether names are returned.

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?

A single eight-word sentence with the resource and scope front-loaded and no filler whatsoever. Nothing in it is redundant against the title or schema.

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

Completeness3/5

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

For a simple no-parameter enumeration tool with no output schema, the description is enough to call it but not enough to use the result confidently, since the return shape (bare IDs vs. ID-plus-name objects) and the expected usage chain into get_water_level go unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter-level detail is missing because no parameters exist.

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 (list) and resource (BAFU hydro station IDs) with a parenthetical scope covering rivers and lakes. It is distinguishable from measurement-returning siblings like get_water_level, but it does not say how it differs from the many other list_*_stations tools in the set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to call this versus alternatives such as get_water_level, get_water_history, or list_ogd_stations. The word 'IDs' hints that this is an enumeration step preceding a station-specific query, but that dependency is never spelled out.

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