Skip to main content
Glama
evanfoglia

Beach Safety MCP

by evanfoglia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_uv_forecast

Get current and max UV index, risk level, and sun-protection recommendations for any beach by name or coordinates.

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

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.2/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add useful behavior (beach names are auto-geocoded worldwide, coordinates are an alternative input mode) and lists what comes back, but it never states that this is a read-only, non-mutating call, nor what happens on geocoding failure or unknown beaches.

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, front-loaded with purpose, followed by input modes and the sibling routing rule. Every clause earns its place with no redundancy.

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?

No output schema exists, but the description enumerates the returned fields, covers both input modes, and routes to the alternative tool. The only gap is the absence of error/failure behavior and read-only reassurance for a tool with no annotations.

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 optional-if-beach_name-given relationship and the anyOf requirement. The description's examples ('Waikiki', 'Bondi Beach') and geocoding note largely restate the schema, so the 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 the UV index forecast') and enumerates the exact payload (current and max UV index, risk level, sun-protection recommendations). It also distinguishes itself from the sibling get_beach_report, so an agent can route without opening a 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 selection rule: 'Use this when only sun-exposure info is needed; use get_beach_report for the full safety report.' The condition and the named alternative are both present, leaving nothing to inference for the primary routing decision.

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