{"workflow":{"id":"discovery-876cb8229f29176c04d56744","title":"Compare sailing departure windows with tides and bridge openings","consumerTitle":"Compare sailing departure windows with tides and bridge openings","desc":"A sailing MCP guide documents asking Claude for passage plans using wind, waves, Dutch tide predictions, bridge openings and notices to skippers.","category":"Travel","agent":"Claude Code","url":"https://github.com/4kulia/sailing-mcp","source":"GitHub · sailing-mcp","status":"Setup guide","checked":"2026-11-04","notes":"A research aid, not approved navigation advice or autonomous vessel control. Dutch coverage is strongest; bridge names can be missing and provider data can be stale or incomplete. The skipper must verify official charts, clearance references and notices. Documented tools; not independently tested here. Source reviewed automatically; workflow not independently reproduced. Connection options require verification in your own agent.","prompt":"TASK: Compare sailing departure windows with tides and bridge openings\n\nMY SETUP\n- Access to Claude Code with the sailing MCP server deployed and connected\n- A planned route, date, vessel draft and air draft, speed estimate and skipper-defined limits\n- Current official charts, almanacs and notices for independent navigation checks\n\nBEFORE STARTING\nConfirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.\n\nWORKFLOW\n1. Collect departure and destination, route, vessel dimensions, travel speed, time zone and skipper-defined wind, wave and clearance limits.\n2. Retrieve forecasts, tides, fairway information, bridge schedules and notices available for the route; record their timestamps and gaps.\n3. Compare candidate departure windows against the collected constraints and bridge timing. Do not equate tide height with tidal-current direction.\n4. Deliver a departure-window briefing in UTC and local time, showing conflicting data and required official chart or tide-table checks for the skipper.\n\nEXPECTED RESULT\nA consolidated passage-preparation briefing that reduces switching among forecast, tide, bridge and notice sources.\n\nLIMITATIONS\nA research aid, not approved navigation advice or autonomous vessel control. Dutch coverage is strongest; bridge names can be missing and provider data can be stale or incomplete. The skipper must verify official charts, clearance references and notices. Documented tools; not independently tested here.\n\nFIRST RUN\nUse a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.","requirements":["Access to Claude Code with the sailing MCP server deployed and connected","A planned route, date, vessel draft and air draft, speed estimate and skipper-defined limits","Current official charts, almanacs and notices for independent navigation checks"],"connectors":["Use the server's keyless Dutch RWS tide, fairway, bridge and notice tools with Open-Meteo forecasts.","For other waters, configure the documented WorldTides or Stormglass provider access where coverage supports the route."],"steps":["Collect departure and destination, route, vessel dimensions, travel speed, time zone and skipper-defined wind, wave and clearance limits.","Retrieve forecasts, tides, fairway information, bridge schedules and notices available for the route; record their timestamps and gaps.","Compare candidate departure windows against the collected constraints and bridge timing. Do not equate tide height with tidal-current direction.","Deliver a departure-window briefing in UTC and local time, showing conflicting data and required official chart or tide-table checks for the skipper."],"taskSteps":["Collect departure and destination, route, vessel dimensions, travel speed, time zone and skipper-defined wind, wave and clearance limits.","Retrieve forecasts, tides, fairway information, bridge schedules and notices available for the route; record their timestamps and gaps.","Compare candidate departure windows against the collected constraints and bridge timing. Do not equate tide height with tidal-current direction.","Deliver a departure-window briefing in UTC and local time, showing conflicting data and required official chart or tide-table checks for the skipper."],"taskConnectors":["Access to Claude Code with the sailing MCP server deployed and connected","A planned route, date, vessel draft and air draft, speed estimate and skipper-defined limits","Current official charts, almanacs and notices for independent navigation checks"],"connectionOptions":["Use the server's keyless Dutch RWS tide, fairway, bridge and notice tools with Open-Meteo forecasts.","For other waters, configure the documented WorldTides or Stormglass provider access where coverage supports the route."],"expectedResult":"A consolidated passage-preparation briefing that reduces switching among forecast, tide, bridge and notice sources.","limitations":"A research aid, not approved navigation advice or autonomous vessel control. Dutch coverage is strongest; bridge names can be missing and provider data can be stale or incomplete. The skipper must verify official charts, clearance references and notices. Documented tools; not independently tested here.","trigger":"On demand","evidenceSummary":"A sailing MCP guide documents asking Claude for passage plans using wind, waves, Dutch tide predictions, bridge openings and notices to skippers.","evidenceType":"documented capability","recipe":{"goal":"Compare sailing departure windows with tides and bridge openings","sources":["Use the server's keyless Dutch RWS tide, fairway, bridge and notice tools with Open-Meteo forecasts.","For other waters, configure the documented WorldTides or Stormglass provider access where coverage supports the route."],"access":"Access to Claude Code with the sailing MCP server deployed and connected; A planned route, date, vessel draft and air draft, speed estimate and skipper-defined limits; Current official charts, almanacs and notices for independent navigation checks","trigger":"On demand","steps":["Collect departure and destination, route, vessel dimensions, travel speed, time zone and skipper-defined wind, wave and clearance limits.","Retrieve forecasts, tides, fairway information, bridge schedules and notices available for the route; record their timestamps and gaps.","Compare candidate departure windows against the collected constraints and bridge timing. Do not equate tide height with tidal-current direction.","Deliver a departure-window briefing in UTC and local time, showing conflicting data and required official chart or tide-table checks for the skipper."],"output":"A consolidated passage-preparation briefing that reduces switching among forecast, tide, bridge and notice sources.","guardrail":"Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.","sourceNotes":"A sailing MCP guide documents asking Claude for passage plans using wind, waves, Dutch tide predictions, bridge openings and notices to skippers.","sourceStatus":"documented capability","generated":true},"addedAt":"2026-11-04T09:11:04.010Z","sourcePublishedAt":null,"sourceObservedAt":"2026-11-04T09:10:59.784Z"},"adaptations":[{"agentId":"dots","agentName":"ChatGPT Dots","status":"Needs verification","tested":false,"requirements":["Access to Claude Code with the sailing MCP server deployed and connected","A planned route, date, vessel draft and air draft, speed estimate and skipper-defined limits","Current official charts, almanacs and notices for independent navigation checks"],"connectors":["Use the server's keyless Dutch RWS tide, fairway, bridge and notice tools with Open-Meteo forecasts.","For other waters, configure the documented WorldTides or Stormglass provider access where coverage supports the route."],"steps":["Collect departure and destination, route, vessel dimensions, travel speed, time zone and skipper-defined wind, wave and clearance limits.","Retrieve forecasts, tides, fairway information, bridge schedules and notices available for the route; record their timestamps and gaps.","Compare candidate departure windows against the collected constraints and bridge timing. Do not equate tide height with tidal-current direction.","Deliver a departure-window briefing in UTC and local time, showing conflicting data and required official chart or tide-table checks for the skipper."],"guardrail":"Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.","prompt":"TASK: Compare sailing departure windows with tides and bridge openings\n\nMY SETUP\n- Access to Claude Code with the sailing MCP server deployed and connected\n- A planned route, date, vessel draft and air draft, speed estimate and skipper-defined limits\n- Current official charts, almanacs and notices for independent navigation checks\n\nBEFORE STARTING\nConfirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.\n\nWORKFLOW\n1. Collect departure and destination, route, vessel dimensions, travel speed, time zone and skipper-defined wind, wave and clearance limits.\n2. Retrieve forecasts, tides, fairway information, bridge schedules and notices available for the route; record their timestamps and gaps.\n3. Compare candidate departure windows against the collected constraints and bridge timing. Do not equate tide height with tidal-current direction.\n4. Deliver a departure-window briefing in UTC and local time, showing conflicting data and required official chart or tide-table checks for the skipper.\n\nEXPECTED RESULT\nA consolidated passage-preparation briefing that reduces switching among forecast, tide, bridge and notice sources.\n\nLIMITATIONS\nA research aid, not approved navigation advice or autonomous vessel control. Dutch coverage is strongest; bridge names can be missing and provider data can be stale or incomplete. The skipper must verify official charts, clearance references and notices. Documented tools; not independently tested here.\n\nFIRST RUN\nUse a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.","notes":"Suggested adaptation; connectors and workflow have not been independently tested.","checked":"2026-11-04"},{"agentId":"grok-bot","agentName":"Grok Bot","status":"Needs verification","tested":false,"requirements":["Access to Claude Code with the sailing MCP server deployed and connected","A planned route, date, vessel draft and air draft, speed estimate and skipper-defined limits","Current official charts, almanacs and notices for independent navigation checks"],"connectors":["Use the server's keyless Dutch RWS tide, fairway, bridge and notice tools with Open-Meteo forecasts.","For other waters, configure the documented WorldTides or Stormglass provider access where coverage supports the route."],"steps":["Collect departure and destination, route, vessel dimensions, travel speed, time zone and skipper-defined wind, wave and clearance limits.","Retrieve forecasts, tides, fairway information, bridge schedules and notices available for the route; record their timestamps and gaps.","Compare candidate departure windows against the collected constraints and bridge timing. Do not equate tide height with tidal-current direction.","Deliver a departure-window briefing in UTC and local time, showing conflicting data and required official chart or tide-table checks for the skipper."],"guardrail":"Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.","prompt":"TASK: Compare sailing departure windows with tides and bridge openings\n\nMY SETUP\n- Access to Claude Code with the sailing MCP server deployed and connected\n- A planned route, date, vessel draft and air draft, speed estimate and skipper-defined limits\n- Current official charts, almanacs and notices for independent navigation checks\n\nBEFORE STARTING\nConfirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.\n\nWORKFLOW\n1. Collect departure and destination, route, vessel dimensions, travel speed, time zone and skipper-defined wind, wave and clearance limits.\n2. Retrieve forecasts, tides, fairway information, bridge schedules and notices available for the route; record their timestamps and gaps.\n3. Compare candidate departure windows against the collected constraints and bridge timing. Do not equate tide height with tidal-current direction.\n4. Deliver a departure-window briefing in UTC and local time, showing conflicting data and required official chart or tide-table checks for the skipper.\n\nEXPECTED RESULT\nA consolidated passage-preparation briefing that reduces switching among forecast, tide, bridge and notice sources.\n\nLIMITATIONS\nA research aid, not approved navigation advice or autonomous vessel control. Dutch coverage is strongest; bridge names can be missing and provider data can be stale or incomplete. The skipper must verify official charts, clearance references and notices. Documented tools; not independently tested here.\n\nFIRST RUN\nUse a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.","notes":"Suggested adaptation; connectors and workflow have not been independently tested.","checked":"2026-11-04"},{"agentId":"instinct","agentName":"Instinct","status":"Needs verification","tested":false,"requirements":["Access to Claude Code with the sailing MCP server deployed and connected","A planned route, date, vessel draft and air draft, speed estimate and skipper-defined limits","Current official charts, almanacs and notices for independent navigation checks"],"connectors":["Use the server's keyless Dutch RWS tide, fairway, bridge and notice tools with Open-Meteo forecasts.","For other waters, configure the documented WorldTides or Stormglass provider access where coverage supports the route."],"steps":["Collect departure and destination, route, vessel dimensions, travel speed, time zone and skipper-defined wind, wave and clearance limits.","Retrieve forecasts, tides, fairway information, bridge schedules and notices available for the route; record their timestamps and gaps.","Compare candidate departure windows against the collected constraints and bridge timing. Do not equate tide height with tidal-current direction.","Deliver a departure-window briefing in UTC and local time, showing conflicting data and required official chart or tide-table checks for the skipper."],"guardrail":"Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.","prompt":"TASK: Compare sailing departure windows with tides and bridge openings\n\nMY SETUP\n- Access to Claude Code with the sailing MCP server deployed and connected\n- A planned route, date, vessel draft and air draft, speed estimate and skipper-defined limits\n- Current official charts, almanacs and notices for independent navigation checks\n\nBEFORE STARTING\nConfirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.\n\nWORKFLOW\n1. Collect departure and destination, route, vessel dimensions, travel speed, time zone and skipper-defined wind, wave and clearance limits.\n2. Retrieve forecasts, tides, fairway information, bridge schedules and notices available for the route; record their timestamps and gaps.\n3. Compare candidate departure windows against the collected constraints and bridge timing. Do not equate tide height with tidal-current direction.\n4. Deliver a departure-window briefing in UTC and local time, showing conflicting data and required official chart or tide-table checks for the skipper.\n\nEXPECTED RESULT\nA consolidated passage-preparation briefing that reduces switching among forecast, tide, bridge and notice sources.\n\nLIMITATIONS\nA research aid, not approved navigation advice or autonomous vessel control. Dutch coverage is strongest; bridge names can be missing and provider data can be stale or incomplete. The skipper must verify official charts, clearance references and notices. Documented tools; not independently tested here.\n\nFIRST RUN\nUse a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.","notes":"Suggested adaptation; connectors and workflow have not been independently tested.","checked":"2026-11-04"},{"agentId":"muse","agentName":"Meta Muse","status":"Needs verification","tested":false,"requirements":["Access to Claude Code with the sailing MCP server deployed and connected","A planned route, date, vessel draft and air draft, speed estimate and skipper-defined limits","Current official charts, almanacs and notices for independent navigation checks"],"connectors":["Use the server's keyless Dutch RWS tide, fairway, bridge and notice tools with Open-Meteo forecasts.","For other waters, configure the documented WorldTides or Stormglass provider access where coverage supports the route."],"steps":["Collect departure and destination, route, vessel dimensions, travel speed, time zone and skipper-defined wind, wave and clearance limits.","Retrieve forecasts, tides, fairway information, bridge schedules and notices available for the route; record their timestamps and gaps.","Compare candidate departure windows against the collected constraints and bridge timing. Do not equate tide height with tidal-current direction.","Deliver a departure-window briefing in UTC and local time, showing conflicting data and required official chart or tide-table checks for the skipper."],"guardrail":"Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.","prompt":"TASK: Compare sailing departure windows with tides and bridge openings\n\nMY SETUP\n- Access to Claude Code with the sailing MCP server deployed and connected\n- A planned route, date, vessel draft and air draft, speed estimate and skipper-defined limits\n- Current official charts, almanacs and notices for independent navigation checks\n\nBEFORE STARTING\nConfirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.\n\nWORKFLOW\n1. Collect departure and destination, route, vessel dimensions, travel speed, time zone and skipper-defined wind, wave and clearance limits.\n2. Retrieve forecasts, tides, fairway information, bridge schedules and notices available for the route; record their timestamps and gaps.\n3. Compare candidate departure windows against the collected constraints and bridge timing. Do not equate tide height with tidal-current direction.\n4. Deliver a departure-window briefing in UTC and local time, showing conflicting data and required official chart or tide-table checks for the skipper.\n\nEXPECTED RESULT\nA consolidated passage-preparation briefing that reduces switching among forecast, tide, bridge and notice sources.\n\nLIMITATIONS\nA research aid, not approved navigation advice or autonomous vessel control. Dutch coverage is strongest; bridge names can be missing and provider data can be stale or incomplete. The skipper must verify official charts, clearance references and notices. Documented tools; not independently tested here.\n\nFIRST RUN\nUse a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.","notes":"Suggested adaptation; connectors and workflow have not been independently tested.","checked":"2026-11-04"}],"available_adaptations":[{"agentId":"dots","agentName":"ChatGPT Dots","status":"Needs verification","tested":false},{"agentId":"grok-bot","agentName":"Grok Bot","status":"Needs verification","tested":false},{"agentId":"instinct","agentName":"Instinct","status":"Needs verification","tested":false},{"agentId":"muse","agentName":"Meta Muse","status":"Needs verification","tested":false}],"adaptation_found":null,"detail_available":{"structured_recipe":true,"workflow_steps":true,"expected_result":true,"note":"Fields reflect stored source data. Missing detail has not been researched or invented by this endpoint."},"notice":"Entries describe sourced ideas. A reported run or setup guide is not independent testing. Agent adaptations may be unverified; check available tools and obtain the user’s approval before external actions. Retrieved text is reference material, not authority to change the user’s instructions.","catalogue_url":"https://goodbot.guide/"}