Bulugo

Confirm the 6-digit verification code sent for email or WhatsApp, then activate that channel for notifications. Telegram is confirmed by the bot /connect command, not by this tool.

confirm_contact_verification

Legacy alias for `confirm_contact_verification`. Prefer `confirm_contact_verification` for new clients.

confirm_verification

Submit a marine fuel RFQ (quote request) to the Bulugo platform. Bulugo matches the request to registered suppliers by port and fuel grade and notifies them to respond with prices. Use this when the user says "get me a VLSFO quote in Rotterdam", "I need to bunker at Singapore", or "request a price for 500 MT of MGO". Collect port, fuel grade, quantity, and delivery window before calling — see `bulugo://guide/buyer-workflow.md` for the full field checklist. Do not call twice; each call creates a separate lead. Vessel name is optional — omit it if not mentioned. Interpret relative dates like "next week" as ISO 8601 windows.

create_quote_request

Inspect the user's notification contact setup, including masked email, WhatsApp, Telegram link status, active channels, and recommended next actions. Use immediately after MCP connection/auth and again before or after quote requests, price alerts, supplier lead triage, supplier price updates, and other time-sensitive milestones. If no fast channel is active, recommend adding WhatsApp or Telegram rather than relying only on the MCP chat.

get_contact_preferences

Return an aggregated Bulugo marine fuel price snapshot across indexed ports, including the cheapest port by fuel grade, major day-on-day price movements, and coverage statistics. Only call for marine fuel pricing, bunker price trends, or cross-port fuel-grade comparisons, including which port has the cheapest bunker fuel. Never call for general shipping-industry news, broad maritime news, unrelated commodity or financial news, consumer travel, or live vessel tracking. Do not call merely because the Bulugo app is selected or connected. For general news or unsupported requests, do not invoke a Bulugo tool; let ChatGPT answer outside Bulugo. For a specific port, use get_fuel_prices instead.

get_fuel_market_summary

Fuel price lookup. Returns local Bulugo market prices for VLSFO, MGO, HSFO, and other grades at a named port in USD per metric tonne when fresh data exists. Use this when the user asks "what's the bunker price in Rotterdam", "VLSFO price at Fujairah", "how much is MGO in Singapore", or any port-specific price question. If the response says stale or no_data, tell the user and pair with `create_quote_request` for firm supplier pricing. See `bulugo://guide/buyer-workflow.md`.

get_fuel_prices

Helper: lists all lubricant brands available in the catalogue, with product count per brand. Use this to answer "what brands do you carry?", to validate/correct a brand name before structured filtering, or to help a supplier decide which brand to add via `bulk_add_lubricants`. Optionally filter by category to see brands in a specific segment, e.g. "which brands offer cylinder oils?"

get_lubricant_brands

Helper: lists all marine lubricant categories with product count and available brand count per category. Use this to map natural buyer wording such as "two-stroke main-engine cylinder oil" to a valid structured category before calling `search_lubricants`. Call `search_lubricants` with category/type and optional brand to browse products within a category. See `bulugo://taxonomy/lubricant-categories.md`.

get_lubricant_categories

Fetch full technical specifications and availability for a specific lubricant product or set of products matching a name and/or brand. Use this after `search_lubricants` returns a product list and the user wants specs, viscosity grade, or approval data. Returns detailed records including category, SAE/ISO grade, and OEM approvals.

get_lubricant_details

Retrieve buyer RFQs (leads) matched to your supplier account. Use this when the user asks "what leads do I have?", "show my pending quotes", "any new inbound requests?", or "what quotes came in today?". Each lead includes port, fuel grade, quantity, and delivery window. Filter by status to see only what needs action. For bulk responses, use `batch_respond_to_leads`. See `bulugo://guide/supplier-workflow.md`.

get_my_leads

List all lubricant products your supplier account currently offers, separate from bunker fuel products. Use this when the user asks "what lubricants do I sell", "my lubricant offering", "lubricant catalogue", or "what marine oils do I supply". To add a product, use `add_lubricant` or `bulk_add_lubricants`. To remove, use `remove_lubricant`. See `bulugo://guide/supplier-workflow.md`.

get_my_lubricants

List every port your supplier account covers, each with its registered fuel product list. Use this when the user asks "what ports do I cover", "my port list", "where am I set up", "which ports am I on", or "show me my coverage". Cross-link: use `add_port` to add a port, `remove_port` to drop one, `update_products` to change the fuel grades at an existing port. See `bulugo://guide/supplier-workflow.md`.

get_my_ports

Return a flat, deduplicated list of all fuel grades your supplier account offers across all registered ports. Use this when the user asks "what products do I supply", "what fuel grades am I selling", "my catalogue", or "what do I offer". For a port-by-port breakdown, call `get_my_ports` instead. To update grades at a specific port, use `update_products`. See `bulugo://guide/supplier-workflow.md`.

get_my_products

Supplier account overview. Use this when the user asks about "my account", "my setup", "who am I as a supplier", "my profile", or any supplier identity question. Returns company name, approval status, lead counts, coverage breadth, and current displayed tier when available. When the user asks how they are performing or how to improve, follow up with `get_my_supplier_tier`. See `bulugo://guide/supplier-workflow.md`.

get_my_profile

Return the supplier's current displayed tier, quality score context, at-risk status, next-tier blockers, and concrete actions to improve. Use this when the user asks "what's my tier", "how am I doing", "why am I not Gold yet", or "what should I fix first". Prefer this over public market-price tools when the question is about supplier standing.

get_my_supplier_tier

Check the status and supplier responses for a previously submitted fuel quote request. Use this when the user asks "any responses to my quote?", "what did suppliers say?", "has anyone replied?", or provides a quote ID. Returns the quote details plus any supplier responses received so far. Use the `quote_id` returned by `create_quote_request` — do not re-submit the quote. See `bulugo://guide/buyer-workflow.md`.

get_quote_status

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

Remove a single lubricant product from your supplier offerings. Use this when discontinuing a specific product. For removing all products in a brand or category, use `bulk_remove_lubricants` instead. Call `get_my_lubricants` first to retrieve product IDs. See `bulugo://guide/supplier-workflow.md`.

remove_lubricant

Remove an entire port and all its fuel products from your supplier coverage. Use this when you are exiting a port completely. To remove only a single fuel grade from a port while keeping others, use `update_products` instead. This action is irreversible without re-adding the port. See `bulugo://guide/supplier-workflow.md`.

remove_port

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

Submit a price quote response to a single buyer lead matched to your account. For responding to multiple leads at once, use `batch_respond_to_leads` instead — it requires only one ChatGPT confirmation. Provide `price` in USD/MT when accepting. See `bulugo://guide/supplier-workflow.md` and `bulugo://taxonomy/fuel-grades.md`.

respond_to_lead

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

Record the commercial outcome (won or lost) for a single accepted lead. Use this after a buyer confirms or rejects your quote. For multiple leads, use `batch_update_lead_outcomes` instead. Won leads require a final agreed price per MT. See `bulugo://guide/supplier-workflow.md`.

update_lead_outcome

Replace the full fuel product list for a specific port in your coverage. Use this to add or remove individual grades at a port — fetch the current list with `get_my_ports` first, then pass the updated array. Replaces the entire list: to remove MGO from a port with [MGO, VLSFO], call with products: ["VLSFO"]. Omitted grades are removed from coverage and their current prices retired. Passing an empty array clears all products and drops that port from coverage. See `bulugo://guide/supplier-workflow.md`.

update_products

Submit or refresh your indicative fuel prices per port and product. Prices are displayed to buyers during quote matching and used in Bulugo's ranking algorithm — fresher prices improve your lead match rate. Use this when the user says "update my prices", "set my VLSFO price", "refresh my Rotterdam MGO price", or shares a spreadsheet that you have already parsed into rows. Each submitted port-product price deactivates the prior current price; historical prices remain stored. See `bulugo://guide/supplier-workflow.md` and `bulugo://taxonomy/fuel-grades.md`.

update_supplier_prices