Skip to main content
Glama

get_water_level

Retrieve current water level and temperature data for Swiss rivers and lakes using hydrological station IDs.

Instructions

Get current river or lake water level and temperature at a Swiss hydrological station

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stationYesHydro station ID (e.g. 2135 for Aare/Bern, 2243 for Rhine/Basel)

Implementation Reference

  • The handler implementation for the get_water_level tool, which fetches latest hydrological data from the API and formats the response.
    case "get_water_level": {
      const url = buildUrl(`${BASE}/hydro/latest`, {
        locations: args.station as string,
        app: "mcp-swiss",
        version: "0.1.0",
      });
      const data = await fetchJSON<ApiResponse>(url);
      const payload = data?.payload;
      if (Array.isArray(payload)) {
        const readings = extractReadings(payload);
        return JSON.stringify({ station: args.station, readings });
      }
      return JSON.stringify(data, null, 2);
    }
  • The tool registration and schema definition for get_water_level within the weatherTools list.
    {
      name: "get_water_level",
      description: "Get current river or lake water level and temperature at a Swiss hydrological station",
      inputSchema: {
        type: "object",
        required: ["station"],
        properties: {
          station: { type: "string", description: "Hydro station ID (e.g. 2135 for Aare/Bern, 2243 for Rhine/Basel)" },
        },
      },
    },
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 mentions the tool retrieves 'current' data, implying it's a read-only operation, but does not disclose behavioral traits such as rate limits, authentication needs, error handling, or data freshness. This leaves gaps for a tool that likely queries external APIs.

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 core purpose ('Get current river or lake water level and temperature') and specifies the context ('at a Swiss hydrological station'). There is no wasted wording, and it is appropriately sized for a simple tool with one parameter.

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's low complexity (one parameter, no output schema, no annotations), the description is minimally complete. It covers the basic purpose but lacks details on behavioral aspects like error cases or return format, which are important for an agent to use it correctly. Without annotations or output schema, more context would be beneficial.

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?

The schema description coverage is 100%, with the parameter 'station' well-documented in the schema (including examples like '2135 for Aare/Bern'). The description does not add meaning beyond this, as it only reiterates the station context without providing additional syntax or format details. The baseline score of 3 is appropriate given the high schema coverage.

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 ('Get current river or lake water level and temperature') and the resource ('at a Swiss hydrological station'), making the purpose specific and unambiguous. It distinguishes itself from siblings like 'get_water_history' (historical data) and 'list_hydro_stations' (listing stations), avoiding redundancy.

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 by specifying 'current' data, suggesting it's for real-time queries rather than historical analysis. However, it lacks explicit guidance on when to use this tool versus alternatives like 'get_water_history' or 'list_hydro_stations', and does not mention prerequisites or exclusions.

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