perigee_analyze_catch_history
ChatGPTDescribe up to 100 recent personal catch records, including zeros and recorded effort. Requires fishing:read. Returns totals, species counts and catch per recorded hour only where effort exists. States pagination and sampling bias; never turns personal logs into a bite forecast or claims causation.
perigee_check_coastal_trip
ChatGPTUse this when the user has a NOAA tide-prediction station ID and wants one activity-specific planning read for a station-local date and time within seven days. It combines tide, daylight, wind, water, astronomy, freshness, and missing-data context, then renders Perigee Tides & Conditions. It is a planning aid, never navigation, emergency guidance, a comprehensive weather forecast, route clearance, a safety verdict, water-quality or public-health clearance, booking, or purchasing. It cannot save a plan, monitor conditions, schedule a recheck, send an alert, or notify the user later.
perigee_compare_fishing_windows
ChatGPTCompare two to six constrained station/date fishing sessions within the next seven days. Supply method, local availability, duration and wind limits for every option. Recommends only fully covered eligible windows, explains tradeoffs and preserves failed options. Use for weekend, morning/evening or nearby-water comparisons; never interpret the ranking as bite probability.
perigee_find_coastal_station
ChatGPTUse this only when the user explicitly needs a public NOAA tide-prediction station for an in-scope, near-term coastal outing read. Do not invoke it for navigation or routing, booking or purchasing, water-quality or public-health questions, safety certification or verdicts, emergency guidance, comprehensive forecasts, or unrelated place searches. Pass a public NOAA tide-station name or distinctive leading portion of that name, a seven-digit station ID, or a two-letter state code; for example, San Francisco can match SAN FRANCISCO (Golden Gate). If no station value is supplied, the tool may use ChatGPT's optional coarse location hint. Do not ask for a raw place phrase, city field, street address, or coordinates. The tool returns no coordinates.
perigee_get_fishing_brief
ChatGPTUse this when the user wants to plan a coastal fishing trip, compare today's or an upcoming day's fishing windows, or understand the tide, first light, last light, and forecast wind at a public NOAA tide-prediction station. Find the station with perigee_find_coastal_station if needed. Returns the same fishing brief as the Perigee website, a suggested window with reasons, alternatives, tide events, daylight, wind, sources, freshness, and missing data. Dates are station-local, today through seven days ahead. These are planning windows, not bite predictions, species reports, catch guarantees, regulations, or safety clearance. Use the method, availability, duration and optional wind limits to constrain the plan. Active advisories and incomplete wind coverage can prevent a recommendation. Account tools separately save explicitly requested plans and catches.
perigee_get_fishing_context
ChatGPTRead supporting marine forecast, recent observed water temperature, optional explicitly selected NOAA current predictions, official regional rule/species references and a method-specific preparation checklist for a fishing session. Provide the same plan constraints as the brief. Never substitute tide high/low for current slack, infer species presence, or declare a catch legal from reference links. No account is required.
perigee_list_fishing_catches
ChatGPTRead a page of up to 100 private catch and zero-catch entries from the connected Perigee account. Follow nextCursor to read more. Requires fishing:read; returns the same records as web/mobile.
perigee_list_fishing_trips
ChatGPTRead up to 50 saved fishing trips from the connected Perigee account. Requires fishing:read. Includes planned and completed trips; does not alter or monitor them.
perigee_list_saved_waters
ChatGPTRead the connected angler's saved NOAA waters across Perigee web and mobile. Requires fishing:read; never accepts an owner ID.
perigee_log_fishing_catch
ChatGPTWrite only the catch or zero-catch session the user explicitly asks to record. Requires fishing:write. Include a stable clientMutationId, count (zero permitted), species (required for fish), time, public water name, method, release status and optional effort minutes. Reuse the ID on retries; conflicting changes fail instead of duplicating. Never invent a catch or effort.
perigee_resolve_fishing_water
ChatGPTResolve a public coastal town, water name, state, or NOAA station ID to up to six NOAA tide references. Returns ambiguity and representativeness guidance. Never invent access, species, current equivalence or fishing spots. Clarify multiple candidates before choosing. Optional coordinates must identify a public water explicitly supplied by the user.
perigee_save_fishing_trip
ChatGPTSave the specific supported fishing window the user explicitly chooses to their Perigee trips. Use the station/date/constraints and window ID from their brief, a trip name and stable clientMutationId. Requires fishing:write and respects the account's trip limit. Retries must reuse the same save ID. Does not automatically save a water, book anything, or enable notifications.
perigee_save_fishing_water
ChatGPTSave a public NOAA reference to the connected angler's existing Perigee waters only when the user explicitly asks. Duplicate saves are idempotent. Does not save device location, create a trip, or subscribe to alerts.
