conditions_compare_days
ChatGPTRank up to 7 consecutive days at one place by bite score (default), verdict (overall or for one discipline) or water clarity, with tide coefficient, lowest low, moon and a wind/wave headline per day. Use for "best day to fish this weekend", "today or Thursday?", "clearest day this week". Name the days with dates and let the server resolve them: "this weekend" -> dates: ["weekend"]; "today or Thursday" -> dates: ["today", "thursday"]; or use from + days for a run of days. Days with no weather forecast (beyond the ~14-day horizon, or not available) are marked astroOnly and rank last for verdict and clarity. Include a clickable link to place.url exactly as returned, including the query string. GO/marginal/NO are conditions ratings for planning, not safety; say so. Bite score is fish activity, not a discipline conditions score.
conditions_get_day
ChatGPTOne place, one day: bite score and best windows, go/marginal/no verdict per discipline (shore, boat, rock, kayak, spearfishing) with reasons, tide, sun, moon and solunar periods, wind and sea summary, water-clarity estimate, and how fresh the forecast is. Use for "is tomorrow good for…", "why is Saturday poor", "too rough today?", "water temperature now" (include hourly). Peskio has no current or slack-water data: never infer them from tide times. Surface temperature and clarity only: no temperature or visibility at depth or thermocline; never infer them. Include a clickable link to the returned place.url with its query string unchanged. State the returned planning disclaimer when giving GO/marginal/NO; never assess whether a crossing, dive or trip is safe.
places_get_profile
ChatGPTWhat a place is: tide regime and range, coast exposure and which wind/swell directions it is sheltered from or exposed to, distance to the nearest river mouth, nearby places and landmarks. Use for "is X sheltered from a north wind?", "big or small tides here?" and "near a river mouth?". Does not cover species, depth or dive sites.
places_search
ChatGPTResolve a town, beach, harbour or cove name to Peskio placeIds (Europe, North Africa and US coasts). Call this first whenever the user names a place, then pass the placeId to the other tools. candidates[0] is the best match: when ambiguous is false, use it without asking (a harbour or beach listed after a town of the same name is part of that place). Ask which one the user means only when ambiguous is true (the same name in different regions). Never ask the user for coordinates.
spots_find_best
ChatGPTRank up to 10 places within 5-25 km of a centre place for one day, on a given local hour or on each place's best daylight hour, by bite score, verdict or water clarity. Use for "where near X is best tomorrow", "best spot at 7 am", "clearest water near Y". For "near me" omit placeId; if that fails, ask the user for a town or beach name. For regions wider than 25 km call it at several named centres. Link every recommended spot using its returned url exactly, query string included. Returned place names can be ambiguous across regions. Exact coordinates are unavailable in these ranked results. GO/marginal/NO are conditions ratings for planning, not safety; say so.
tides_get_table
ChatGPTTide times, heights and Peskio coefficient estimates for one place over up to two weeks, with sunrise, sunset, daylight low tides and moon phase. Use for tide times, spring/neap tides, grandes marées, pêche à pied, tidal islands and boat launching. Heights are in metres above the stated datum. Information only: for tidal crossings, tell the user to follow the official crossing schedule. Peskio has no tidal-current or slack-water data: never derive them from these times. Explicitly label coefficients as Peskio estimates in the user language (French: estimation Peskio). Include a clickable link to place.url exactly as returned, query string included.
