Skip to main content
Glama
evanfoglia

Beach Safety MCP

by evanfoglia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_uv_forecast

Check the UV index forecast for any beach by name or coordinates. Get current and max UV levels, risk rating, and sun-protection guidance to plan safer time in the sun.

Instructions

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.

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.7/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 well by disclosing the geocoding behavior ('auto-geocoded worldwide'). It also enumerates the returned data fields. It stops short of stating failure modes (e.g., what happens on an unresolvable beach name) or rate limits, which keeps it at 4 rather than 5.

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?

Three sentences, front-loaded with purpose and scope, then input modes, then the sibling routing. Every sentence carries distinct load and none 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?

The tool is simple (0 required params, no output schema), and the description covers purpose, inputs, return values, and sibling differentiation. Nothing an agent needs to call it correctly is missing, and the absence of an output schema is compensated by enumerating the returned fields.

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 baseline is 3, but the description adds value by clarifying the two input modes and the auto-geocoding (e.g., "just say 'Waikiki'"), and that providing beach_name or coordinates is sufficient. This is meaningful semantic guidance beyond the raw schema types.

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+resource ('Get the UV index forecast for any beach') and enumerates the returned data: current and max UV index, risk level, and sun-protection recommendations. It also distinguishes itself from the sibling get_beach_report, so an agent can disambiguate immediately.

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 scopes when to use it ('Use this when only sun-exposure info is needed') and names the alternative (get_beach_report) for the broader case. This is exactly the when/when-not/alternative structure that earns a 5.

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