Skip to main content
Glama

NOAA Tides and Currents

by io.github.RyanCardin15
OverviewAdmin

Find Nearest NOAA Stations

noaa_find_nearest_stations
Read-onlyIdempotent

Find the NOAA stations closest to a latitude/longitude point, sorted by distance.

Use this to answer "what's the tide station near ?" — geocode the place to coordinates first, then call this. Filter by type to match the data you need (e.g. type "tidepredictions" before calling noaa_get_tide_predictions, "currents" before noaa_get_currents — current stations have different IDs than water-level stations).

Distance is computed great-circle (Haversine) and reported in both km and miles. (NOAA's API has no native coordinate search; this tool maintains a cached station directory.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoStation capability filter. Common: "waterlevels" (active water level), "tidepredictions", "currents" (observed currents), "currentpredictions", "met" (weather sensors). Full list via noaa_get_reference_guide topic "station_types".
limitNoNumber of stations to return.
latitudeYesLatitude in decimal degrees (-90 to 90).
longitudeYesLongitude in decimal degrees (-180 to 180).
max_distance_kmNoOptional cutoff radius in kilometers.
response_formatNoOutput format: "markdown" for a readable summary table, "json" for the complete structured payload.markdown

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds technical detail (Haversine computation, km/miles reporting, cached station directory) and mentions output format options. No contradiction.

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?

Five sentences with clear sections: purpose, usage example, technical note. No redundant information. Well-structured and efficient.

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

Completeness4/5

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

All 6 parameters are explained. Output behavior (sorted by distance, km/miles) is covered. No output schema exists, but description gives sufficient summary. Some detail about response fields could be added, but acceptable.

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

Parameters4/5

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

Schema coverage is 100%. Description adds value by explaining type filter examples, default limit, max_distance_km as optional cutoff, and response_format options. Adds context beyond schema.

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?

Description starts with a clear verb+resource: 'Find the NOAA stations closest to a latitude/longitude point, sorted by distance.' It uniquely identifies the tool's function and distinguishes it from siblings like noaa_search_stations.

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 explicit usage context: geocode first, filter by type, and links to sibling tools (e.g., noaa_get_tide_predictions). Missing explicit 'when not to use' but covers key usage scenarios.

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

All NOAA Tides and Currents toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources