Skip to main content
Glama

get_river_water_levels

Read-onlyIdempotent

Retrieve observed water levels, danger thresholds, flood margins, and flood status across 44 Bangladesh river stations from FFWC/BWDB. Use for live hydrology, flood monitoring, or river danger checks. For static river lengths and origins without live water levels, use get_bd_geography_catalog instead. Read-only, updated every 2 hours. Returns station name, river, basin, district, water_level_m, danger_level_m, margin_m, and status (NORMAL, WARNING, ABOVE_DANGER).

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional filter matching river name, monitoring station, basin (Brahmaputra, Ganges, Meghna, South Eastern Hill), or district. Omit to return all 44 stations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / query / description
      Previous value: -"River name, station, basin, or district"New value: +"Optional filter matching river name, monitoring station, basin (Brahmaputra, Ganges, Meghna, South Eastern Hill), or district. Omit to return all 44 stations."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint. The description adds useful context beyond those annotations by naming the data source, stating the two-hour update frequency, and listing the returned fields and status values. It does not discuss authentication or rate limits, but the key behavioral profile is well covered.

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 front-loaded with the core purpose, followed by usage guidance, sibling differentiation, freshness, and return fields. Every sentence contributes useful information without repetition or wasted wording.

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

Completeness5/5

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

Although there is no output schema, the description explicitly lists the returned fields and status values. Combined with rich annotations, a single optional parameter, and a clear data source and update cadence, the definition gives an agent everything needed to call the tool correctly.

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%, and the query parameter is fully documented in the schema with examples for river name, station, basin, and district. The description does not add further meaning beyond the schema, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: retrieve observed water levels, danger thresholds, flood margins, and flood status across 44 Bangladesh river stations from FFWC/BWDB. It clearly distinguishes the tool from the static geography catalog sibling.

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

Usage Guidelines5/5

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

It gives explicit use cases: live hydrology, flood monitoring, and river danger checks. It also names the alternative tool for static river lengths and origins without live water levels, making the routing decision unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources