Environment Agency Flood Monitoring MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_flood_warningsA | Get current flood warnings and alerts. Updated every 15 minutes. |
| get_flood_warningC | Get details of a specific flood warning by ID |
| get_flood_areasC | Get flood areas (regions where warnings/alerts may apply) |
| get_flood_areaB | Get details of a specific flood area by area code |
| get_monitoring_stationsC | Get monitoring stations that measure water levels, flows, etc. |
| get_monitoring_stationC | Get detailed information about a specific monitoring station |
| get_measuresC | Get measurement types available across all stations |
| get_station_measuresC | Get all measurement types available from a specific station |
| get_readingsA | Get measurement readings from all stations. Updated every 15 minutes. |
| get_measure_readingsC | Get readings for a specific measurement type |
| get_station_readingsC | Get all readings from a specific monitoring station |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes targeting specific resources like flood areas, warnings, stations, or readings, with clear boundaries. However, some overlap exists between get_readings (all stations) and get_station_readings (specific station), which could cause minor confusion if not carefully read.
All tools follow a consistent verb_noun pattern with 'get_' prefix, using snake_case throughout. The naming is highly predictable and readable, making it easy for agents to understand the action and target resource.
With 11 tools, the count is well-scoped for a flood monitoring domain, covering key resources like areas, warnings, stations, and readings. Each tool appears to earn its place without feeling excessive or insufficient.
The toolset provides comprehensive read-only coverage for monitoring flood data, including areas, warnings, stations, and readings. A minor gap is the lack of tools for historical data queries or subscription/alert management, but core real-time monitoring workflows are well-supported.