Flood

Get Flood Forecast

get_flood_forecast

Read-onlyIdempotent

Get multi-day flood forecast for a location with current, mean, and peak river discharge projections. Returns discharge statistics and severity assessment. Use to evaluate flood risk and timeline.

Input Schema

TableJSON Schema

Name	Required	Description
`latitude`	Yes	Latitude of the location in decimal degrees.
`longitude`	Yes	Longitude of the location in decimal degrees.
`forecast_days`	No	Number of forecast days to retrieve (1–92). Defaults to 16.

Output Schema

TableJSON Schema

Name	Required	Description
`days`	Yes	Array of daily flood forecast data
`units`	Yes	Unit labels for each daily variable
`latitude`	Yes	Latitude of the location in decimal degrees
`timezone`	Yes	Timezone name for the location
`longitude`	Yes	Longitude of the location in decimal degrees

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "days": {
+      "description": "Array of daily flood forecast data",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "ISO date string",
+            "type": "string"
+          },
+          "river_discharge": {
+            "description": "Current river discharge in cubic meters per second",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "river_discharge_max": {
+            "description": "Maximum river discharge in cubic meters per second",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "river_discharge_mean": {
+            "description": "Mean 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"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "latitude": 40.7128,
+    "longitude": -74.006
+  },
+  {
+    "forecast_days": 30,
+    "latitude": 35.6762,
+    "longitude": 139.6503
+  }
+]

First observedApr 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavioral context by specifying the nature of the data returned: multi-day forecast with current/mean/peak projections and severity assessment. This goes beyond the annotations and helps the agent understand what to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences and front-loaded with the purpose. The second sentence ('Returns discharge statistics and severity assessment') is slightly redundant with the first, but each sentence contributes useful information. It is efficient without being excessively verbose.

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?

With output schema present and annotations covering safety, the description is complete for tool selection and invocation. It clearly states the input (location) and the purpose (flood risk/timeline), and the output schema defines return values. No further context is needed.

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%, so the baseline is 3. The description mentions 'location' but does not elaborate on forecast_days or provide additional parameter context beyond the schema. It adds no meaningful parameter semantics beyond what is already in the schema.

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 uses a specific verb 'Get' with a clear resource: 'multi-day flood forecast for a location,' and details the outputs (current, mean, and peak river discharge projections, discharge statistics, severity assessment). This distinguishes it from siblings like get_river_discharge, which likely focuses on current discharge only.

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

Usage Guidelines4/5

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

The description explicitly states when to use: 'Use to evaluate flood risk and timeline.' It provides clear context for the primary use case, though it does not name alternative tools or provide exclusions. This qualifies as clear context without explicit alternatives, warranting a 4.

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

All Flood tools Inspect

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.