MCP server providing access to NOAA CO-OPS tide predictions, water level data, and station information
Server has 4 tools with complete input schemas and descriptions, but quality is inconsistent. Tool names follow verb_noun pattern (get_*, search_*) which is good. Descriptions are present but generic (avg ~80 chars, below 194-char baseline). Parameters lack enums for constrained values (datum, time_zone, units, interval). No output schema documentation. Error handling returns raw exceptions instead of actionable guidance. No tool annotations (readOnlyHint, etc.). Composition is reasonable, each tool has single responsibility. Missing parameter validation rules in descriptions (e.g., station_id format, date format constraints).
Get information about a specific station using the NOAA CO-OPS Metadata API.
Get tide predictions for a specific station.
Get water level data for a specific station.
Search for stations by name or location.
No enum constraints for constrained parameters. 'datum', 'time_zone', 'units', and 'interval' accept free-form strings, inviting hallucinated values. Should declare enums: datum=[MLLW, NAVD88, ...], time_zone=[gmt, lst, ldt], units=[english, metric], interval=[hilo, h, 6min, ...].
Error handling returns raw exception strings (e.g., 'return {"error": str(e)}') instead of actionable recovery guidance. LLM cannot determine if error is retryable, user-fixable, or fatal. Should categorize errors and suggest next steps.
No output schema documentation. Descriptions state 'Returns: Dictionary containing...' but do not specify field names, types, or structure. LLM cannot plan downstream calls or extract required data (e.g., station_id for chaining).
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | <=2025-11-25 | v2 |
Parameter descriptions lack format/constraint details. 'station_id: The 7-digit station ID' does not specify format (must be numeric, exactly 7 chars?). 'begin_date: Start date in yyyyMMdd format' is good, but 'expand: List of additional resources' lacks valid enum values (details, sensors, datums, products?).
No tool annotations. Tools are read-only but lack readOnlyHint annotation. This prevents clients from optimizing caching, retry logic, or permission checks.