Skip to main content
Glama
cmer81

Open-Meteo MCP Server

by cmer81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Flood Forecast

flood_forecast
Read-onlyIdempotent

Retrieve river discharge and flood forecasts from GloFAS for specified coordinates and dates.

Instructions

Get river discharge and flood forecasts from GloFAS (Global Flood Awareness System).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dailyNo
modelsNoOmit to use the default model.
end_dateNoDate in YYYY-MM-DD format.
ensembleNoReturn all 50 ensemble members instead of a single series.
latitudeYes
timezoneNoIANA time zone (e.g. "Europe/Paris"), or "auto" for the location's own. Default GMT.
longitudeYes
past_daysNoDays before today to include, in addition to the forecast.
start_dateNoDate in YYYY-MM-DD format.
timeformatNoiso8601
forecast_daysNoDays to forecast, starting today.
cell_selectionNoGrid cell to use near a coastline: prefer "land", prefer "sea", or the "nearest" cell.nearest

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changedv2.5.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / cell_selection
      Added value: +{
+  "default": "nearest",
+  "description": "Grid cell to use near a coastline: prefer \"land\", prefer \"sea\", or the \"nearest\" cell.",
+  "enum": [
+    "land",
+    "sea",
+    "nearest"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / daily / description
      Removed value: -"River discharge variables to retrieve"
    • addedInput schema / properties / end_date
      Added value: +{
+  "description": "Date in YYYY-MM-DD format.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • changedInput schema / properties / ensemble / description
      Previous value: -"If true, all forecast ensemble members will be returned"New value: +"Return all 50 ensemble members instead of a single series."
    • removedInput schema / properties / forecast_days / default
      Removed value: -92
    • changedInput schema / properties / forecast_days / description
      Previous value: -"Number of forecast days (up to 210 days possible)"New value: +"Days to forecast, starting today."
    • changedInput schema / properties / forecast_days / maximum
      Previous value: -210New value: +366
    • changedInput schema / properties / forecast_days / minimum
      Previous value: -1New value: +0
    • removedInput schema / properties / latitude / description
      Removed value: -"Latitude in WGS84 coordinate system"
    • removedInput schema / properties / longitude / description
      Removed value: -"Longitude in WGS84 coordinate system"
    • addedInput schema / properties / models
      Added value: +{
+  "description": "Omit to use the default model.",
+  "enum": [
+    "seamless_v4",
+    "forecast_v4",
+    "consolidated_v4",
+    "seamless_v3",
+    "forecast_v3",
+    "consolidated_v3"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / past_days / description
      Previous value: -"Include past days data"New value: +"Days before today to include, in addition to the forecast."
    • changedInput schema / properties / past_days / maximum
      Previous value: -7New value: +92
    • changedInput schema / properties / past_days / minimum
      Previous value: -1New value: +0
    • addedInput schema / properties / start_date
      Added value: +{
+  "description": "Date in YYYY-MM-DD format.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / timeformat
      Added value: +{
+  "default": "iso8601",
+  "enum": [
+    "iso8601",
+    "unixtime"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / timezone / description
      Previous value: -"Timezone for timestamps"New value: +"IANA time zone (e.g. \"Europe/Paris\"), or \"auto\" for the location's own. Default GMT."
  2. First observedv1.1.3

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds essentially nothing beyond that: it does not disclose the ensemble-vs-single-series behavior, model variants, global coverage limits, or forecast horizon, all of which are behaviorally relevant.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the brevity is also what leaves the other dimensions thin.

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

Completeness2/5

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

For a 12-parameter tool with no output schema, the description is far too thin. An agent has no signal about defaults, ensemble output shape, temporal ranges, or how this differs from the other forecast tools, so it is under-specified relative to the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Twelve parameters with only 67% schema description coverage, and the description explains none of them. Key semantics like what ensemble=true returns (50 members) or which models are available are left entirely to the schema, so the description does nothing to close the remaining coverage gap.

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?

States a specific verb and resource ('Get river discharge and flood forecasts') and names the source system GloFAS, which cleanly distinguishes it from the weather/air-quality/elevation siblings. It doesn't explicitly call out the sibling contrast, but the resource is unique enough in this tool set.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives such as weather_forecast or the model-specific forecast siblings. The agent is left to infer that this is the flood/river-discharge option on its own.

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

Deploy Server

Other Tools