Skip to main content
Glama

Flood

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get River Discharge

get_river_discharge
Read-onlyIdempotent

Get daily river discharge forecast in cubic meters per second for a location. Returns discharge values with timestamps. Use to monitor water flow rates for flood risk assessment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesLatitude of the location in decimal degrees.
longitudeYesLongitude of the location in decimal degrees.
forecast_daysNoNumber of forecast days to retrieve (1–92). Defaults to 7.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysYesArray of daily forecast data
unitsYesUnit labels for each daily variable
latitudeYesLatitude of the location in decimal degrees
timezoneYesTimezone name for the location
longitudeYesLongitude of the location in decimal degrees

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "days": {
+      "description": "Array of daily forecast data",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "ISO date string",
+            "type": "string"
+          },
+          "river_discharge": {
+            "description": "River discharge in cubic meters per second",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "date"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "latitude": {
+      "description": "Latitude of the location in decimal degrees",
+      "type": "number"
+    },
+    "longitude": {
+      "description": "Longitude of the location in decimal degrees",
+      "type": "number"
+    },
+    "timezone": {
+      "description": "Timezone name for the location",
+      "type": "string"
+    },
+    "units": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Unit labels for each daily variable",
+      "type": "object"
+    }
+  },
+  "required": [
+    "latitude",
+    "longitude",
+    "timezone",
+    "units",
+    "days"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "latitude": 40.7128,
+    "longitude": -74.006
+  },
+  {
+    "forecast_days": 14,
+    "latitude": 48.8566,
+    "longitude": 2.3522
+  }
+]
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful context about units and timestamps but does not clarify openWorld implications or any additional behavioral details beyond the annotations.

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?

Three sentences, front-loaded with the core function, then unit and use case. No redundancy or unnecessary details; every sentence contributes value.

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

Completeness4/5

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

With a complete input schema and an output schema present, the description covers the primary purpose and use case. Minor gap: no mention of the related flood forecast tool, but the description is sufficiently complete for a simple read-only data fetch.

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 100%, so parameters are fully described in the schema. The description adds the unit of measurement and forecast nature but does not elaborate on parameter semantics beyond what the schema provides.

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?

The description clearly states the tool retrieves daily river discharge forecasts in cubic meters per second for a location, with a specific resource and verb. It differentiates from siblings by specifying discharge rather than flood forecasts, though it does not explicitly distinguish from get_flood_forecast.

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?

Provides a usage context: 'Use to monitor water flow rates for flood risk assessment.' However, it does not mention when not to use it or compare with the closely related sibling get_flood_forecast, leaving some ambiguity for tool selection.

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

All Flood toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources