noaa-marine-mcp-server

Get Ocean Current Profile

noaa_marine_get_current_profile

Read-only

Observed ocean-current depth profile from an NDBC ADCP buoy — the most recent measurement of current speed and direction at each depth bin, returning depth in meters, direction in degrees true (the direction the current flows toward), and speed in cm/s. It is distinct from noaa_marine_get_currents, which returns CO-OPS tidal-current predictions of max flood, ebb and slack rather than these observed acoustic-Doppler measurements. A depth bin is reported whenever NDBC gives it a depth, and its direction or speed is null when the sensor did not report that component. Use noaa_marine_find_stations with source="ndbc" and types=["current_profile"] to find station IDs, since most NDBC stations serve no ADCP profile and an unfiltered search returns IDs this tool cannot read.

Input Schema

Name	Required	Description	Default
`station_id`	Yes	NDBC station ID (mostly 5-character alphanumeric codes, e.g. "44033"; some are 7-digit numbers). Obtain from noaa_marine_find_stations with source="ndbc" and types=["current_profile"].

Output Schema

Name	Required	Description
`bins`	No	Depth-binned current measurements, shallowest first (NDBC source order).
`error`	No	Present when the call failed. Absent on success.
`source`	No	Data source — always "ndbc" for this tool.
`latitude`	No	Station latitude in decimal degrees. Null when the station is absent from the NDBC active-stations list — the ADCP feed carries current data but no coordinates.
`bin_count`	No	Number of depth bins in the profile.
`longitude`	No	Station longitude in decimal degrees. Null when the station is absent from the NDBC active-stations list.
`station_id`	No	Station ID echoed from the request — for chaining.
`observed_at`	No	ISO 8601 UTC timestamp of the observation. Always a valid instant — a row whose upstream time columns are malformed is rejected rather than timestamped with the current time.
`station_name`	No	Station name from the NDBC active stations list.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / station_id / description

Previous value: -"NDBC station ID (5-character alphanumeric, e.g. \"44033\"). Obtain from noaa_marine_find_stations with source=\"ndbc\" and types=[\"current_profile\"]."New value: +"NDBC station ID (mostly 5-character alphanumeric codes, e.g. \"44033\"; some are 7-digit numbers). Obtain from noaa_marine_find_stations with source=\"ndbc\" and types=[\"current_profile\"]."

Changed1 schema field changedSep 17, 2026

changedOutput schema / properties / observed_at / description

Previous value: -"ISO 8601 UTC timestamp of the observation."New value: +"ISO 8601 UTC timestamp of the observation. Always a valid instant — a row whose upstream time columns are malformed is rejected rather than timestamped with the current time."

Changed8 schema fields changedSep 16, 2026
- removedOutput schema / properties / bins / items / properties / direction_deg / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / bins / items / properties / direction_deg / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / bins / items / properties / speed_cm_s / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / bins / items / properties / speed_cm_s / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / latitude / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / latitude / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / longitude / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / longitude / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed6 schema fields changedAug 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "station_id",
+      "station_name",
+      "latitude",
+      "longitude",
+      "observed_at",
+      "source",
+      "bin_count",
+      "bins"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `profile_not_found`: NDBC returned 404 for the station — no ADCP current-profile file exists for it. `no_current_data`: The ADCP file exists but has no usable data rows — profiler offline or every bin missing. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "profile_not_found",
+            "no_current_data"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "station_id",
-  "station_name",
-  "latitude",
-  "longitude",
-  "observed_at",
-  "source",
-  "bin_count",
-  "bins"
-]

AddedJul 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With readOnlyHint=true and openWorldHint=true already covering the safety profile, the description adds important behavioral context: it is an observed acoustic-Doppler measurement rather than a prediction, depth bins appear only when NDBC provides a depth, and missing direction/speed components are null. This goes beyond the annotations and is directly useful for interpreting calls and results.

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?

The description is front-loaded with the core definition and then adds only distinctions, null semantics, and station-discovery guidance that matter for correct use. There is no filler or repetition that would obscure the key points.

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?

For a single-parameter read-only tool with an output schema and safety annotations, the description is complete enough to select and invoke it correctly. It covers purpose, sibling differentiation, valid station discovery, return semantics, and null-component behavior.

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

Parameters3/5

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

Schema description coverage is 100%, and the single station_id parameter is already well documented in the schema, including its expected source and format. The description reinforces how to find valid station IDs but does not add new parameter syntax or constraints beyond the schema, so the baseline 3 is appropriate.

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?

The description states a specific observed resource: the most recent NDBC ADCP ocean-current depth profile, with current speed/direction per depth bin. It explicitly distinguishes this from noaa_marine_get_currents, which returns CO-OPS tidal-current predictions, so an agent can select it without opening other schemas.

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

Usage Guidelines5/5

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

It explicitly says to use noaa_marine_find_stations with source="ndbc" and types=["current_profile"] to obtain station IDs. It also explains why unfiltered station searches are a problem: most NDBC stations do not serve ADCP profiles, so this tool cannot read them.

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

All noaa-marine-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.