noaa-tidesandcurrents-mcp

Get NOAA API Reference Guide

noaa_get_reference_guide

Read-onlyIdempotent

Retrieve curated NOAA CO-OPS reference topics—datums, units, data limits, intervals—to build correct tide and current API requests.

Instructions

Get curated reference documentation for NOAA CO-OPS concepts and parameters. Topics:

products: Every NOAA CO-OPS data product and which tool serves it
datums: Vertical datums (MLLW, MSL, IGLD...) and station applicability
units: What english vs metric means per measurement (incl. cm/s currents)
time_zones: gmt / lst / lst_ldt semantics and restrictions
intervals: Valid interval values per product family
station_types: Station type filters and station ID formats
data_limits: Maximum date-range span per product
quality_flags: Data quality fields (v/s/f/q), flag letters, HH/H/L/LL
date_formats: Accepted date formats and parameter combinations
marine_forecast: NWS wind & marine forecast tools vs CO-OPS observations

Consult this before constructing unusual requests — especially "datums" (which vertical reference to use and station applicability), "units" (english/metric asymmetries like cm/s current speeds), and "data_limits" (maximum date spans per product).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`topic`	Yes	Reference topic to retrieve.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`guide`	Yes
`topic`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.1Oct 5, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds that the content is curated reference material and enumerates topics, but does not disclose format, length, or other operational traits; with strong annotations, this is useful but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, followed by a well-structured topic list where each bullet adds distinct selection value. No filler; appropriate length for a 10-topic reference tool.

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

Completeness5/5

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

Given that output schema handles return values and annotations cover the safety profile, the description provides complete selection guidance for this reference tool. Nothing an agent needs to call the tool correctly is missing.

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

Parameters5/5

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

Schema coverage is 100% and the single enum parameter is documented in the schema, but the description goes well beyond by explaining what each of the 10 topic values contains. This meaningfully improves topic selection.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('curated reference documentation for NOAA CO-OPS concepts and parameters'), then makes the scope explicit by listing all covered topics. This is clearly distinct from the sibling data-retrieval tools.

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

Usage Guidelines4/5

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

Provides when-to-consult guidance ('Consult this before constructing unusual requests') and highlights three high-value topics. It does not name alternatives or exclusions explicitly, so it falls short of a 5.

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