Skip to main content
Glama

flood_forecast

Read-onlyIdempotent

Retrieve river discharge flood forecasts for a specified latitude and longitude from Open-Meteo, with optional forecast days up to 92.

Instructions

Get river discharge flood forecast from Open-Meteo.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "flood_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoForecast days (default 7, max 92).
latitudeYesLocation latitude.
longitudeYesLocation longitude.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without description help. The description adds only the provenance ('Open-Meteo'), and says nothing about return units (e.g. m³/s), model resolution, or forecast horizon behavior beyond what the schema states.

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 zero filler or redundancy. It is arguably terse to the point of leaving value on the table, but nothing in it is wasted.

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?

With only 3 fully-documented parameters, annotations covering safety, and no output schema, the definition is technically callable as written. However, for a forecast tool the agent gets no signal about units, spatial resolution, or global-vs-regional coverage, which are the details that affect interpreting results.

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% — latitude, longitude and days are all documented in-schema, including the default-7/max-92 bound on days. The description adds nothing beyond the schema for any parameter, so the baseline of 3 applies.

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+resource ('Get river discharge flood forecast') plus the upstream provider (Open-Meteo), so the agent knows exactly what data comes back. It does not differentiate from the many nearby weather siblings (weather_forecast, marine_forecast, air_quality_forecast, historical_weather), which is the only thing keeping it from a 5.

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?

There is no guidance on when to prefer this over weather_forecast or marine_forecast, and no stated preconditions or geographic coverage limits. The only usage signal is implicit in the phrase 'river discharge flood', which the agent must infer means hydrological rather than general weather forecasting.

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