KaiCast Ocean Conditions

Recommend spots

recommend_spot

Read-onlyIdempotent

Ranked top picks (max 5) for an activity in one area on one day — by region id, or lat+lon with a radius. Each pick has the best daylight window, why (from the published conditions), a confidence score with its factors, caveats, and a KaiCast spot card. Returns status "not_covered" / "conditions_only" / "activity_not_modeled" honestly instead of guessing. Activities: snorkel (native model), dive, freedive, spearfish (proxy model; spots in water closed to spearfishing are excluded), surf (not modeled). Free during early access.

Input Schema

Name	Required	Description
`lat`	No	Latitude, decimal degrees. Use with lon.
`lon`	No	Longitude, decimal degrees. Use with lat.
`date`	No	Spot-local day to plan for. Default: today, or tomorrow once today's daylight has passed. Up to 6 days ahead.
`spot`	No	Spot id, e.g. "hanauma-bay".
`limit`	No	How many picks (default 3, max 5).
`region`	No	Region id, e.g. "us-hi-oahu".
`activity`	Yes	What the user wants to do.
`radius_km`	No	Search radius around lat/lon in km (default 40, max 100).

Output Schema

Name	Required	Description	Default
`picks`	Yes
`schema`	Yes
`source`	Yes
`status`	Yes
`message`	No
`coverage`	Yes
`disclaimer`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 28, 2026
- addedOutput schema / properties / picks / items / properties / card / properties / cta / properties / url / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / picks / items / properties / card / properties / cta / properties / url / type
```
Removed value: -"string"
```
- addedOutput schema / properties / picks / items / properties / card / properties / links / properties / app / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / picks / items / properties / card / properties / links / properties / app / type
```
Removed value: -"string"
```
- addedOutput schema / properties / picks / items / properties / card / properties / links / properties / forecast / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / picks / items / properties / card / properties / links / properties / forecast / type
```
Removed value: -"string"
```
- addedOutput schema / properties / picks / items / properties / card / properties / links / properties / share / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / picks / items / properties / card / properties / links / properties / share / type
```
Removed value: -"string"
```

Changed2 schema fields changedOct 7, 2026

removedOutput schema / properties / cards

Removed value: -{
-  "items": {
-    "additionalProperties": {},
-    "properties": {
-      "cta": {
-        "additionalProperties": {},
-        "properties": {
-          "label": {
-            "type": "string"
-          },
-          "url": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "label",
-          "url"
-        ],
-        "type": "object"
-      },
-      "date": {
-        "type": "string"
-      },
-      "links": {
-        "additionalProperties": {},
-        "properties": {
-          "app": {
-            "type": "string"
-          },
-          "forecast": {
-            "type": "string"
-          },
-          "share": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "share",
-          "app",
-          "forecast"
-        ],
-        "type": "object"
-      },
-      "score": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "spot_id": {
-        "type": "string"
-      },
-      "spot_name": {
-        "type": "string"
-      },
-      "tier": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "tier_label": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "spot_id",
-      "spot_name",
-      "tier",
-      "tier_label",
-      "score",
-      "date",
-      "links",
-      "cta"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

changedOutput schema / required

Previous value: -[
-  "schema",
-  "status",
-  "coverage",
-  "cards",
-  "disclaimer",
-  "source",
-  "picks"
-]New value: +[
+  "schema",
+  "status",
+  "coverage",
+  "disclaimer",
+  "source",
+  "picks"
+]

Changed2 schema fields changedOct 6, 2026

changedInput schema / properties / region / description

Previous value: -"Region id from list_coverage, e.g. \"us-hi-oahu\"."New value: +"Region id, e.g. \"us-hi-oahu\"."

changedInput schema / properties / spot / description

Previous value: -"Spot id from list_coverage or get_conditions, e.g. \"hanauma-bay\"."New value: +"Spot id, e.g. \"hanauma-bay\"."

Changed2 schema fields changedOct 6, 2026

changedInput schema / properties / region / description

Previous value: -"Region id, e.g. \"us-hi-oahu\"."New value: +"Region id from list_coverage, e.g. \"us-hi-oahu\"."

changedInput schema / properties / spot / description

Previous value: -"Spot id, e.g. \"hanauma-bay\"."New value: +"Spot id from list_coverage or get_conditions, e.g. \"hanauma-bay\"."

Changed2 schema fields changedOct 6, 2026

changedInput schema / properties / region / description

Previous value: -"Region id from list_coverage, e.g. \"us-hi-oahu\"."New value: +"Region id, e.g. \"us-hi-oahu\"."

changedInput schema / properties / spot / description

Previous value: -"Spot id from list_coverage or get_conditions, e.g. \"hanauma-bay\"."New value: +"Spot id, e.g. \"hanauma-bay\"."

First observedOct 6, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: discloses that results cap at 5, shows confidence factors and caveats, and explicitly states it returns honest 'not_covered' / 'conditions_only' / 'activity_not_modeled' statuses instead of guessing. It also flags model fidelity (snorkel native; dive/freedive/spearfish proxy; surf unmodeled), the exclusion of spots in closed waters, and free early-access pricing.

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

Conciseness4/5

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

Front-loads the core promise (ranked top picks, area, day) before enumerating return fields and activity coverage. The middle sentence is a dense list of returned fields but each item is informative; no filler sentences.

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?

An output schema exists so return values needn't be explained, yet the description still usefully characterizes statuses and confidence. With 8 params it covers location modes, activity fidelity, and limit, but leaves the standalone 'spot' parameter and how it combines with region/lat-lon unaddressed.

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%, so the schema carries parameter mechanics; the description adds semantic value the schema cannot, notably the native-vs-proxy-vs-unmodeled mapping for each activity enum value. It also reiterates the 5-pick cap and the mutually exclusive region vs lat+lon+radius framing without spelling out precedence.

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 — 'Ranked top picks (max 5) for an activity in one area on one day' — plus the two ways to specify the area (region id, or lat+lon with radius). An agent can immediately tell this returns ranked spot recommendations, distinct from a date-ranking or condition-lookup tool.

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

Usage Guidelines3/5

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

Usage context is implied rather than stated: it explains supported activities and location modes, but never says when to choose this over best_day, best_months, get_conditions, or list_coverage. The 'not_covered'/'activity_not_modeled' statuses implicitly signal when the tool can't answer, but the agent must infer the routing rules.

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

All KaiCast Ocean Conditions 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.

Resources

Need Help?