Skip to main content
Glama
evanfoglia

Beach Safety MCP

by evanfoglia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_surf_forecast

Get focused surf conditions for a beach by name or coordinates: wave height, period, direction, swell, rip current risk, and safety score. Use when only surf data is needed.

Instructions

Get a focused surf forecast for any beach: wave height, wave period and direction, swell height/period/direction, rip current risk, and safety score. Accepts a beach name (auto-geocoded worldwide — just say 'Waikiki' or 'Bondi Beach') or raw coordinates. Use this when only surf conditions are needed; use get_beach_report for the full safety report including wind, temperature, and UV.

Input Schema

NameRequiredDescriptionDefault
latitudeNoLatitude in decimal degrees (optional if beach_name is given)
longitudeNoLongitude in decimal degrees (optional if beach_name is given)
beach_nameNoName of the beach (e.g., 'Waikiki', 'Bondi Beach, Sydney'). Auto-geocoded — provide this or latitude/longitude.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.4
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "beach_name"
+    ]
+  },
+  {
+    "required": [
+      "latitude",
+      "longitude"
+    ]
+  }
+]
    • removedInput schema / required
      Removed value: -[]
  2. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / beach_name
      Added value: +{
+  "description": "Name of the beach (e.g., 'Waikiki', 'Bondi Beach, Sydney'). Auto-geocoded — provide this or latitude/longitude.",
+  "type": "string"
+}
    • removedInput schema / properties / lat
      Removed value: -{
-  "type": "number"
-}
    • addedInput schema / properties / latitude
      Added value: +{
+  "description": "Latitude in decimal degrees (optional if beach_name is given)",
+  "type": "number"
+}
    • removedInput schema / properties / lon
      Removed value: -{
-  "type": "number"
-}
    • addedInput schema / properties / longitude
      Added value: +{
+  "description": "Longitude in decimal degrees (optional if beach_name is given)",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "lat",
-  "lon"
-]New value: +[]
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden; it discloses genuinely useful behavioral context by describing the return payload composition and the auto-geocoding input behavior ('auto-geocoded worldwide — just say Waikiki'). It omits failure modes for unresolvable beach names, rate limits, and auth requirements, which leaves some burden uncovered for a no-annotation tool.

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?

Two sentences, each earning its place: the first is a front-loaded purpose statement with the output inventory, the second covers input handling and sibling routing. No filler or redundancy.

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?

There is no output schema, but the description enumerates the returned fields explicitly and explains the mutually exclusive input modes, so an agent has everything needed to call it correctly. The absence of annotations is partially compensated by the returned-data and geocoding details.

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%, so the schema already documents all three parameters including the anyOf beach_name-or-coordinates constraint. The description restates auto-geocoding and gives examples but adds no new syntax, format, or precedence rules beyond what the schema provides; baseline 3 applies.

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 ('Get a focused surf forecast for any beach') and enumerates the exact outputs returned (wave height/period/direction, swell metrics, rip current risk, safety score). It explicitly distinguishes itself from the sibling get_beach_report, so an agent can route between them without opening either schema.

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?

Explicitly states when to use it ('when only surf conditions are needed') and names the alternative with the condition that selects it ('use get_beach_report for the full safety report including wind, temperature, and UV'). This is a direct when/when-not/alternative pairing.

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

Deploy Server

Other Tools