Skip to main content
Glama

NS Pros MCP Gateway

noaa-ndbc__ndbc_station_history

Recent observation time series for one NDBC station, up to the last ~45 days of standard meteorological rows at the station reporting interval (usually every 10 minutes for buoys, hourly for some partners). Use for trends: "how has wave height changed this week", "was there a wind event on the 3rd". Sourced from NOAA NDBC realtime observations.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hours": 6,
      "limit": 20,
      "station_id": "46026"
    },
    "name": "noaa-ndbc__ndbc_station_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoOnly rows within this many hours of the newest one (default 24, max 1080)
limitNoMax rows to return, newest first (default 200, max 2000)
station_idYesNDBC station id, e.g. "46026"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does disclose the retention window (~45 days), typical cadence (10 min buoys, hourly partners), and data provenance (NDBC realtime observations). It does not say what happens for stations with sparse/absent rows or what units/columns appear, so the disclosure is strong but not complete.

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?

Three compact sentences: resource and window first, usage examples second, provenance last. Every clause earns its place and nothing is repeated from structured fields.

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?

For a three-parameter read-only time-series tool with no output schema, the definition covers scope, retention, cadence, and intended queries. It is slightly thin on return shape (which meteorological fields, units, handling of gaps), which an agent estimating row volume or downstream processing would want.

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 coverage is 100%, with defaults and maxima already documented for hours and limit, so the schema does the heavy lifting. The description only adds that the time step depends on the station's reporting interval, which is useful context for choosing hours but not parameter-level detail.

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 and resource — 'recent observation time series for one NDBC station' — and bounds it to ~45 days of standard meteorological rows at the station cadence. That is enough for an agent to distinguish it from a latest-observation snapshot without opening the schema.

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?

The description gives concrete use cases ('how has wave height changed this week', 'was there a wind event on the 3rd') that make the trend/history role explicit, which implicitly rules out point-in-time lookups. It stops short of naming the sibling (e.g. ndbc_latest_obs) or stating when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.