Bulugo

Read-only supplier onboarding guidance. Use when a new or anonymous supplier asks what Bulugo does for suppliers, how to join as a supplier, how to add ports/products/prices, or how supplier leads work. This is guidance only: it must not create buyer quote requests, supplier accounts, leads, notifications, or external messages. See `bulugo://guide/supplier-workflow.md`.

get_supplier_onboarding

Retrieve the current durable Bulugo support handoff status and any stored human replies for this authenticated MCP or ChatGPT account. Use after request_human_support, or when the user asks whether the support team has replied. This is the truthful return path for non-push MCP clients.

get_support_handoff_status

Helper: returns all port names that have live fuel pricing data in the Bulugo database. Use this when the user asks "which ports do you cover?", "what ports have prices?", or before calling `get_fuel_prices` to confirm a port name is recognised. Do not call this when the user already knows their port — call `get_fuel_prices` directly. See `bulugo://guide/buyer-workflow.md`.

list_fuel_ports

Helper: lists supported canonical ports in the Bulugo port catalogue. Use this to help the user discover valid port names before calling `plan_route`, `check_route_alternatives`, or supplier coverage tools. Supports region and country filters. For live fuel prices at a port, use `get_fuel_prices`. For route distance and bunkering options, use `plan_route` or `check_route_alternatives`. See `bulugo://guide/route-bunker-workflow.md`.

list_route_ports

Generate a short-lived, single-use login link for the authenticated user. Only call when the user explicitly asks to access their Bulugo account or web portal, including a named dashboard section such as ports, leads, usage, or developer settings. Never call as a fallback for unsupported requests such as travel booking, general news, or live vessel tracking. Do not call merely because the Bulugo app is selected or connected. For unsupported requests, do not invoke a Bulugo tool; explain the limitation and let ChatGPT answer outside Bulugo.

open_bulugo_account_dashboard

Calculate maritime route geometry between two ports. Returns distance in nautical miles, estimated voyage time, and a route map image. Use this when the user asks "how far is Singapore to Rotterdam?", "how long is the voyage?", or "show me the route". For fuel price comparisons at ports along the route, use `check_route_alternatives` instead — it handles both geometry and REAL live prices in one call. See `bulugo://guide/route-bunker-workflow.md`.

plan_route

Record explicit authenticated buyer consent for Bulugo RFQ supplier matching and terms after `create_quote_request` returns BUYER_CONSENT_REQUIRED. Use this only after the user clearly agrees to both required consents in the current conversation. Pass the `resume_token` from the blocked quote response; the tool records an auditable consent event and returns `resume_arguments` for exactly one follow-up `create_quote_request` call without re-entering RFQ details.

record_buyer_quote_consent

Create a durable Bulugo human support handoff from this MCP or ChatGPT conversation. Use when the user explicitly asks for a human, support team, real person, representative, callback, or live agent. This returns an honest acknowledgement in the current tool response; future human replies are retrieved with get_support_handoff_status because MCP is not a push chat channel.

request_human_support

Structured marine lubricant catalogue search across 1,700+ products. Use only with valid brand and category/type filters discovered from `get_lubricant_brands` and `get_lubricant_categories`; do not pass natural-language or free-text buyer requests. Returns product names, grades, and brand. Pair with `get_lubricant_details` for full specs and `request_lubricant_quote` to submit a quote request. See `bulugo://taxonomy/lubricant-categories.md` for category definitions.

search_lubricants

Check supplier availability at a port for a given fuel grade. Returns a count of registered suppliers — not individual names (privacy-safe). Use this when the user asks "are there suppliers in Hamburg for MGO?", "how many suppliers cover VLSFO in Fujairah?", or before submitting an RFQ to confirm the port+product combination has coverage. To submit an RFQ, use `create_quote_request`. See `bulugo://guide/buyer-workflow.md`.

search_suppliers

Start verification for a contact channel. For email or WhatsApp, sends a 6-digit code and should be followed by `confirm_contact_verification`. For Telegram, creates safe /connect instructions; usernames alone are not enough because Bulugo must have a linked bot chat id before it can send Telegram notifications.

send_contact_verification

Legacy alias for `send_contact_verification`. Prefer `send_contact_verification` for new clients, especially for Telegram /connect setup.

send_verification

Save notification contact preferences — email, WhatsApp, and/or a Telegram username label — plus notification types and preferred/active channels. Use when the user wants quote, lead, or price alerts. Telegram usernames are labels only; Telegram notifications are inactive until `send_contact_verification` with channel=telegram creates a /connect code and the user messages the Bulugo bot.

update_contact_preferences