Skip to main content
Glama

List FOEN hydrology stations

list_hydro_stations
Read-only

List FOEN river and lake monitoring stations with IDs and water bodies, optionally filtered by water body or place name such as 'Aare' or 'Bern'.

Instructions

List FOEN river/lake monitoring stations with their IDs and water bodies. Optionally filter by name (river, lake or place).

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
limitNo
queryNoFilter by water body or place name, e.g. 'Aare' or 'Bern'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.3/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 adds that results carry station IDs and water bodies, but says nothing about pagination or that the default limit truncates the list to 25 entries, which matters for a list tool.

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, front-loaded with the resource and scope, then the optional filter. No filler and nothing redundant.

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 two-parameter read-only list tool with no output schema, the description covers what is returned in outline. It is incomplete on the practical point that results are capped by a default limit of 25, and it gives no hint of the total set size or how to retrieve more.

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 50%: query is documented in the schema, and the description usefully extends it to 'river, lake or place'. The limit parameter gets no mention at all in the description, so its default of 25 and maximum of 100 are left for the agent to discover in the schema.

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 and resource ('List FOEN river/lake monitoring stations') plus the returned fields (IDs and water bodies), which is far more than a restated title. It does not distinguish itself from related siblings such as search_stations or get_nearby_stations, so an agent must infer which listing tool to pick.

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?

The only guidance is 'Optionally filter by name', which describes a parameter rather than when to choose this tool. With siblings named search_stations and get_nearby_stations present, the absence of any routing or exclusion guidance is a real gap.

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