Beach Safety MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_beach_reportA | Get comprehensive beach safety conditions including rip current risk, waves, swell, wind, temperature, UV, and safety score for any beach location. Automatically geocodes any beach name worldwide — just say 'Waikiki' or 'Bondi Beach'. |
| get_beach_jsonA | Get beach conditions as structured JSON for programmatic use. Same as get_beach_report but in JSON format. Auto-geocodes any beach name. |
| get_surf_forecastA | 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. |
| get_uv_forecastA | Get the UV index forecast for any beach: current and max UV index, risk level, and sun-protection recommendations. Accepts a beach name (auto-geocoded worldwide — just say 'Waikiki' or 'Bondi Beach') or raw coordinates. Use this when only sun-exposure info is needed; use get_beach_report for the full safety report. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
get_beach_report, get_surf_forecast, and get_uv_forecast have distinct, well-explained scopes with explicit guidance on when to use each. The main ambiguity is get_beach_json vs get_beach_report, which return the same data in different formats, so an agent could trivially misselect between them.
All four tools follow a clean get_<noun>_<format> snake_case pattern (get_beach_json, get_beach_report, get_surf_forecast, get_uv_forecast). Naming is fully predictable and consistent.
Four tightly scoped tools easily fit the beach safety domain, and each earns its place (full report, JSON variant, surf focus, UV focus). No bloat or missing core capability at this count.
Coverage of conditions, surf, and UV is solid for a beach safety surface, but tide tables, water quality, and hazard advisories are absent. These are minor gaps an agent can work around but are relevant for full beach safety.