noaa-tidesandcurrents-mcp
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_water_levelsC | Get water level data for a station |
| get_tide_predictionsC | Get tide prediction data |
| get_currentsC | Get currents data for a station |
| get_current_predictionsC | Get current predictions |
| get_meteorological_dataC | Get meteorological data |
| get_stationsC | Get list of stations |
| get_station_detailsC | Get detailed information about a station |
| get_moon_phaseB | Get moon phase information for a specific date |
| get_moon_phases_rangeC | Get moon phase information for a date range |
| get_next_moon_phaseC | Get the next occurrence(s) of a specific moon phase |
| get_sun_timesB | Get sun rise/set and other sun event times for a specific date and location |
| get_sun_times_rangeB | Get sun rise/set and other sun event times for a date range and location |
| get_sun_positionB | Get sun position information for a specific date, time, and location |
| get_next_sun_eventB | Get the next occurrence(s) of a specific sun event |
| get_parameter_definitionsB | Get information about valid parameter values for NOAA API requests |
| get_sea_level_trendsC | Get sea level trends and error margins for a station |
| get_extreme_water_levelsC | Get extreme water levels and exceedance probabilities for a station |
| get_high_tide_flooding_dailyC | Get high tide flooding daily count data for a station |
| get_high_tide_flooding_monthlyB | Get high tide flooding monthly count data for a station |
| get_high_tide_flooding_seasonalC | Get high tide flooding seasonal count data for a station |
| get_high_tide_flooding_annualC | Get high tide flooding annual count data for a station |
| get_high_tide_flooding_projectionsC | Get high tide flooding decadal projections for sea level rise scenarios |
| get_high_tide_flooding_likelihoodsB | Get high tide flooding daily likelihoods for a station |
| get_top_ten_water_levelsB | Get top ten highest or lowest water levels for a 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 24 tools
Most tools have clearly distinct purposes targeting specific data types like tides, currents, water levels, flooding, sun/moon events, and station metadata. However, some potential overlap exists between 'get_current_predictions' and 'get_currents' (both related to currents) and among the multiple high tide flooding tools (daily, monthly, seasonal, annual), though their descriptions help differentiate timeframes.
All 24 tools follow a consistent 'get_*' verb_noun pattern with snake_case, making them predictable and readable. The naming convention is uniform throughout, with no deviations in style or structure.
With 24 tools, the count is borderline high for a focused domain like NOAA tides and currents data. While it covers many specific data types, it might feel heavy compared to typical well-scoped servers (3-15 tools), potentially overwhelming agents with numerous similar options.
The tool set provides comprehensive coverage for the NOAA tides and currents domain, including station lookup, various water/current/tide data, flooding projections, sun/moon events, and metadata. There are no obvious gaps; agents can access all relevant data types and workflows without dead ends.