TameWind

Connect your AI assistant

Your AI assistant can plan passages with TameWind: your boat, your comfort levels, the latest forecasts. Add TameWind to it once, sign in with your TameWind account and allow what it may do. Then ask, for example: “Plan a passage from Falmouth to Saint Peter Port tomorrow at 8.”

The address to give it: https://tamewind.com/mcp

To see or disconnect an assistant: Settings › Account › Connected AI assistants in TameWind.

For the assistant

TameWind plans sailing passages for the sailor's own boat: its polar, its motoring rule and its comfort levels, on the latest ECMWF forecast and its ensemble, the same as the TameWind app.

Plan a passage

1. Find both ends: find_place with each name gives a position in decimal degrees (or use a position the sailor gives). Several places can share a name: pick by the waters each lies on, or ask the sailor.
2. Optional: get_my_boat says the boat, its comfort levels and the time zone answers use.
3. Route: route_passage with from, to, departure ("now", a local time, or a sweep of up to 4 departures) and level (fastest, moderate or gentle; none for the sailor's own default).
4. If the answer says "routing", call route_passage again with exactly the same arguments after about a minute; it counts once. If it says "busy", ask again in a minute.
5. Tell the sailor: quote the summary as it is, the arrival and its range across the forecasts, how many forecasts stay within each comfort level, and the forecast run.
6. To open the plan in the TameWind app, call open_passage with the plan_id, and always give the sailor the link it returns.
7. For the weather at a position, at the boat or along the plan, ask get_weather.

Good to know

• Units: wind and gusts in knots, waves in metres, distances in nautical miles, speeds in knots. Positions in decimal degrees. Wind directions are true, the direction the wind blows from.
• Times: every answer uses the sailor's time zone and names it. A departure time without an offset is in that zone.
• Comfort levels: fastest, moderate and gentle are the boat's limits for wind, gusts and waves; a level holds when the route stays within them.
• A point on land moves to the nearest open water within 10 nm; the answer gives the point used and its name.
• A route call waits up to 40 seconds. One route at a time per sailor.
• Daily limits per sailor: 20 routes, 100 weather questions, 10 feedback messages.
• Every answer is a planning aid, not for navigation: say so once, and never tell the sailor to sail or not to sail. Describe the conditions; the skipper decides.
• send_feedback only with the sailor's own words, and only when the sailor asks.

Tools

• route_passage: Route a passage with the sailor's boat, polar and comfort levels on the current forecast, as the TameWind app does. Give from and to as decimal degrees (find_place turns a harbour or island name into one; TameWind moves a point on land to the nearest open water within 10 nm and echoes the point it used with its own name for it). departure: "now", a time (ISO 8601; without an offset, the sailor's zone), or {"first", "every_h" (3, 6, 12 or 24), "count" (1 to 4)} for a sweep. level: fastest, moderate or gentle, the boat's comfort limits for wind, gusts and waves (null: the sailor's default). Times in the answer are in the sailor's zone, which it names; wind in knots, waves in metres, distance in nautical miles. The call waits up to 40 seconds. The answer per departure: arrival and its range across the ensemble forecasts, distance, duration, average speed, how many forecasts stay within each comfort level's limits, highest wind, gusts and waves, upwind share, motoring and night hours. If it says routing, call again with the same arguments in about a minute: the same request returns the same plan and counts once; if it says busy, ask again in a minute. Quote the summary as it is; it describes the passage and never says whether to go.
• get_my_boat: The sailor's boat as TameWind routes it: name, polar recipe and its factors, motoring rule, comfort levels with their limits (wind and gusts in knots, waves in metres), the default level, and the time zone every answer uses.
• find_place: Look up a harbour, coastal town or island by name and get its position in decimal degrees for route_passage and get_weather. Several places can share a name: each result says the waters it lies on (a sea, an island group or an ocean); pick the one the sailor means, or pass near (a position) to put the nearest first, and ask the sailor when it is still unclear. A town's position is the town itself, often on land: route_passage moves it to the nearest open water within 10 nm. Accents and case do not matter; St, Ste and Mt read as Saint, Sainte and Mount.
• get_weather: The forecast wind, gusts, waves and rain, hour by hour, at a position, at the boat (its last tracked position, under 3 hours old), or along a plan from route_passage (each hour at the boat's planned position). The window is tonight (sunset to sunrise there), now (the next few hours) or {"from", "to"} times, at most 48 hours. Give positions as decimal degrees (find_place turns a name into one). Wind and gusts in knots, waves in metres, times in the sailor's zone, named in the answer. The values are the ones the TameWind app shows; name the forecast run and the spread when you answer.
• send_feedback: Send feedback to the TameWind team with the sailor's account: a bug, an idea or a question. Only when the sailor asks you to send it, and only in the sailor's own words: do not add, summarise or rephrase. Attach a plan from route_passage with "about" when the message is about one. The TameWind team reads it.
• open_passage: Open a plan from route_passage in TameWind on the sailor's own devices, when the sailor asks to open, show or send the passage: each device with TameWind installed and notifications on gets a notification that opens the passage when tapped. Always give the sailor the returned link too: it opens the same passage.
• about_tamewind: What TameWind is and how to plan a passage with it end to end: the order of the tools, units, time zones, comfort levels, limits and what to do on "routing" or "busy". Read it once before the first passage of a conversation.

The same for machines: /llms.txt.