Skip to main content
Glama

list_hydro_stations

Retrieve a comprehensive list of Swiss hydrological monitoring stations for rivers and lakes from BAFU data.

Instructions

List all available BAFU hydrological monitoring stations (rivers and lakes) in Switzerland

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for list_hydro_stations tool.
    case "list_hydro_stations": {
      const url = buildUrl(`${BASE}/hydro/locations`, { app: "mcp-swiss" });
      const data = await fetchJSON<ApiResponse>(url);
      const payload = (data?.payload ?? {}) as Record<string, StationEntry>;
      const stations = compactHydroStations(payload);
      return JSON.stringify({ count: Object.keys(stations).length, stations });
    }
  • Tool registration and schema definition for list_hydro_stations.
    {
      name: "list_hydro_stations",
      description: "List all available BAFU hydrological monitoring stations (rivers and lakes) in Switzerland",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Helper function to format hydro station data.
    function compactHydroStations(payload: Record<string, StationEntry>): Record<string, string> {
      const result: Record<string, string> = {};
      for (const s of Object.values(payload)) {
        const id = s.details?.id ?? s.name;
        const name = s.details?.name ?? id;
        const water = s.details?.["water-body-name"];
        const type = s.details?.["water-body-type"];
        const suffix = [water, type].filter(Boolean).join(", ");
        result[id] = suffix ? `${name} (${suffix})` : name;
      }
      return result;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it lists stations but does not disclose behavioral traits such as whether the data is real-time or historical, if there are rate limits, authentication needs, or what the output format looks like. This leaves significant gaps for an agent to understand how to use the tool effectively.

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?

The description is a single, efficient sentence that front-loads the key information ('List all available BAFU hydrological monitoring stations') without any wasted words. It is appropriately sized for a simple tool with no parameters.

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?

Given the tool has no parameters, no annotations, and no output schema, the description is minimal but adequate for a basic listing operation. However, it lacks details on output format, data freshness, or any constraints, which could be helpful for an agent. It meets the minimum viable standard but has clear gaps in behavioral context.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate here, but it could have mentioned any implicit filters or options, though not required. Baseline is 4 due to zero parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List all available') and the resource ('BAFU hydrological monitoring stations (rivers and lakes) in Switzerland'), making the purpose specific and unambiguous. It distinguishes itself from sibling tools like 'list_air_quality_stations' or 'list_snow_stations' by specifying the type of stations.

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 description implies usage when needing hydrological station data, but it does not explicitly state when to use this tool versus alternatives like 'get_nearby_stations' or 'search_stations', nor does it mention any prerequisites or exclusions. The context is clear but lacks explicit guidance on tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vikramgorla/mcp-swiss'

If you have feedback or need assistance with the MCP directory API, please join our Discord server