Skip to main content
Glama
evanfoglia

Beach Safety MCP

by evanfoglia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_surf_forecast

Fetch surf conditions for any beach by name or coordinates: wave height, period, swell, rip current risk, and safety score. Use for surf-only forecasts.

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

TableJSON 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. 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: +[]
  2. First observedv0.1.0

TDQS

A4.4/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, and it does disclose meaningful behavior: inputs are auto-geocoded worldwide and either a beach name or raw coordinates may be supplied. It does not mention rate limits, caching, or error behavior for unresolvable beach names, which keeps it short of a 5.

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?

Purpose and returned fields are front-loaded, and the sibling routing is placed last where it reads as a decision aid. The enumeration of output fields is slightly list-heavy but each item is a distinct surf metric, so little is wasted.

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?

With no output schema and no annotations, the description compensates fully by naming the returned metrics and explaining the input resolution strategy. An agent has everything needed to invoke it correctly and interpret the result.

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 three parameters are already fully documented and the baseline is 3. The description reinforces the geocoding behavior with examples ('just say Waikiki or Bondi Beach'), but adds no format or constraint detail beyond the schema.

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 exactly which quantities are returned (wave height/period/direction, swell, rip current risk, safety score). It explicitly distinguishes itself from get_beach_report, so an agent can route 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 Guidelines5/5

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

Gives an explicit when-to-use condition ('when only surf conditions are needed') paired with the named alternative ('use get_beach_report for the full safety report including wind, temperature, and UV'). The selecting condition and the excluded case are both stated.

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