coops.tides.conditions
Get observed meteorological data from a NOAA CO-OPS station. Supports five products: air_temperature (°F or °C), water_temperature (sea surface °F or °C), air_pressure (millibars), humidity (relative humidity %), and wind (speed and direction — available at select stations). Returns 6-minute inte...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/coops.tides.conditions.md
What coops.tides.conditions does on Apibase
AI agents call coops.tides.conditions to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Maximum number of recent readings to return (1–500). Readings are at 6-minute intervals. Defaults to 60 (last 6 hours). |
units | string | — | Unit system: english = °F / knots / feet, metric = °C / m/s / meters. Defaults to english. |
product | string | — | Meteorological product to retrieve. air_temperature = air temp in °F (or °C), water_temperature = sea surface temp, air_pressure = barometric pressure in mb, hu |
end_date | string | — | End date for observations in YYYY-MM-DD or YYYYMMDD format (e.g. 2025-07-02). Defaults to today. Maximum range: 31 days. |
begin_date | string | — | Start date for observations in YYYY-MM-DD or YYYYMMDD format (e.g. 2025-07-01). Defaults to yesterday. Maximum range: 31 days. |
station_id | string | Yes | NOAA CO-OPS station ID (4–7 digits, e.g. 8443970 for Boston MA). Find station IDs with the coops.tides.stations tool. |
Parameters from the server's own tool schema.
Why coops.tides.conditions is rated Low
Tool retrieves historical weather observation data with no side effects or modifications.
From the tool's definition Get observed meteorological data from NOAA CO-OPS station. Returns readings, no modifications.
Attacks that exploit this kind of access
The rule that runs coops.tides.conditions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For coops.tides.conditions, this is the rule to start with:
coops.tides.conditions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every coops.tides.conditions call is checked against it from then on.
Questions about coops.tides.conditions
Get observed meteorological data from a NOAA CO-OPS station. Supports five products: air_temperature (°F or °C), water_temperature (sea surface °F or °C), air_pressure (millibars), humidity (relative humidity %), and wind (speed and direction — available at select stations). Returns 6-minute interval readings for the specified date range (default: last 24 hours) plus the most recent reading for quick lookups. Note: not all stations have all sensors — if a product is unavailable at the requested station, the API returns an error. Try station 8443970 (Boston) for air_temperature, 9414290 (San Francisco) for water_temperature. Source: NOAA CO-OPS — tidesandcurrents.noaa.gov. No auth, US Gov public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
coops.tides.conditions accepts 6 parameters: limit, units, product, end_date, begin_date, station_id. Required: station_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for coops.tides.conditions: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Apibase. Nothing to install.
coops.tides.conditions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the coops.tides.conditions rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for coops.tides.conditions. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
coops.tides.conditions is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue