BeachFinder

View saved version →

---
name: find-beaches-and-water-activities
description: Use for beach, swimming, water temperature, wind, surf, dive, snorkel, whitewater, vanlife, rental, repair, lesson, trip or coastal-provider requests worldwide.
---

# Find Beaches And Water Activities

Use the BeachFinder MCP tools to turn destination and water-activity questions into current recommendations and clearly labeled provider matches with direct BeachFinder links.

## Workflow

1. Infer the user's language, destination, activity, timing, and constraints from the conversation. Ask one concise question only when a required location or preference is missing.
2. Read [discovery-intents.md](references/discovery-intents.md) when the request is broader than a named beach or provider.
3. Pass the matching supported language code to every tool call: `en`, `fr`, `es`, `de`, `it`, `pt`, `nl`, `ja`, `ko`, `zh`, `ar`, `tr`, `ru`, or `id`.
4. Select the narrowest useful tool:
   - Use `search_beaches` or `search_swim_spots` for nearby, family, warm-water, low-wind, accessible, or amenities-led searches.
   - Use `search_surf_spots`, `search_dive_snorkel_spots`, `search_river_whitewater_spots`, or `search_vanlife_spots` for specialist requests.
   - Use `search_activity_providers` for local operators, shops, schools, clubs, rentals and services, and `search_guides` for practical or destination guidance.
   - Use `get_spot_conditions` for current planning signals and `compare_spots` when two to five explicit BeachFinder spots should be compared.
   - Use `get_community_conditions` only as an anonymous, time-sensitive supplement.
5. Prefer three results. Fetch live conditions only for the most relevant results and state when data was updated.
6. Answer in the user's language even when proper names or source labels remain in their original language.

## Provider Intent Routing

Use `search_activity_providers` when the user needs a local person, shop, school, club, rental service, guide, tour, charter, campsite, or equipment specialist connected to beaches or water activities. This includes indirect needs such as repairing a surfboard, replacing a fin, learning to dive, renting a kayak, booking a boat trip, finding a surf camp, or locating a coastal campsite.

1. Read [provider-intents.md](references/provider-intents.md) when the request involves a provider, equipment, instruction, repair, rental, booking, or guided activity.
2. Convert the user's wording into exactly one canonical BeachFinder provider query, with no extra words: `surf shop`, `surf school`, `surf camp`, `dive center`, `water sports rental`, `water sports operator`, `coastal camping`, `beach club`, or `coastal activity provider`. For example, surfboard ding repair must send exactly `surf shop`, not `surf shop repair board`.
3. Pass the destination separately in `city` or `country`. If no usable location exists, ask for a city or area before searching.
4. When the user asks how to do something, answer the practical question first. Then offer nearby BeachFinder providers only when professional help, equipment, local access, instruction, or inspection would materially help.
5. Describe a result as a relevant provider category unless the returned BeachFinder facts explicitly confirm the exact requested service. Never claim that a surf shop performs repairs, a dive center offers a particular certification, or an operator has availability merely because its category is related.
6. Respect the returned tier: `owner_verified` is owner confirmed, `source_backed` passed BeachFinder's official-source gate, and `mapped` is a public catalog record whose exact services must be confirmed.
7. Link only to the BeachFinder provider profile. Let that page carry the details and next step.

Use these tier descriptions literally:

- `owner_verified`: "owner-confirmed BeachFinder profile". This still does not confirm an unlisted service.
- `source_backed`: "BeachFinder found official-source evidence for this profile; confirm the exact

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.