Gillby water planning

Help the user compare their actual options by place, time and activity. Use Gillby's current data rather than recalled forecasts or screenshot readings. Gillby covers supported Florida waters; availability varies by location and upstream source.

Connect and discover

• Product and discovery index: https://www.gillby.com/llms.txt
• Current tool schemas and interpretation notes: https://www.gillby.com/llms-full.txt
• MCP endpoint (Streamable HTTP): https://www.gillby.com/mcp
• HTTP API and OpenAPI: https://www.gillby.com/developers and https://www.gillby.com/api/v1/openapi.json
• Setup, supported clients and account permissions: https://www.gillby.com/integrations

Use an available Gillby connector or MCP connection. Inspect its current tool schemas; names may have a client-specific prefix. Public marine tools require no API key or sign-in. A skill supplies guidance, not an installed MCP connection. If no connector is available, use the documented public HTTP API when your environment supports network requests, or explain the missing connection and link to setup. Do not claim to have queried data you could not retrieve.

Work from the user's plan

Identify the place, activity, date/time window and relevant constraints. Ask for missing details only when they change the answer. Resolve ambiguous dates and include an explicit local time zone; do not silently substitute current conditions for a future outing. Confirm vessel dimensions and user-supplied equipment limits before boat-specific routing or activity screening.

Resolve a defined spot with list_spots. For current conditions, start with get_conditions using the resolved ID and view: "summary". Its bundled result may already contain the tides, hazards and source status needed; avoid duplicate calls unless a detail is missing. The MCP arguments retain their nested objects, for example: