get_chef
ChatGPTEverything about one chef in a single call: bio, rating, cuisines, bookable packages with prices and guest limits, menus, add-ons, fees, cancellation policy and recent reviews. Call it after search_chefs and before anything else — package_id and optional_id values appear nowhere else, and every later tool needs them. Omit package_id on the first call: you get menu names and a dish count, enough to talk the customer through the options. Call again with one package_id only once they have narrowed down, to see that package's dishes. Never fetch every package's menus in turn — dishes dominate this payload. Each package charges per its unit, and min_quantity/max_quantity bound what quote_booking accepts. price_per_item is charged per unit, price_fixed once. Shows no availability and reserves nothing.
get_chef_availability
ChatGPTThe dates and start times one chef can still take a booking, for the package the customer is considering. Call it after get_chef, before offering any date. Pass package_id: slot length follows that package's duration, and without it the tool assumes the chef's longest package and returns a conservative set. days holds chef-local wall-clock times (chef_timezone) — present them as returned. slots_utc holds the same instants in ISO-8601 UTC and is the only correct source for reserve_booking.service_datetime_utc. Offer only times this call returned. Do not interpolate, extend past the last one, or round to a nicer hour: reserve_booking re-checks the same calendar and rejects anything else. Best-effort current information, not a held slot. Existing bookings and blocked dates are already subtracted, but this is a weekly schedule rather than a live lock and another customer can take a slot first. If reserving fails on availability, call this again and re-offer. Defaults to 30 days ahead, capped at 90 days and at a fixed slot count.
list_service_cities
ChatGPTThe Brazilian cities where myChef has bookable chefs. Use it when the customer asks where myChef operates, or after search_chefs returned city_candidates or matched nothing. Not a required first step — search_chefs resolves a city name itself. An absent city is one myChef does not serve: say so, rather than offering a nearby one as if it were bookable.
quote_booking
ChatGPTThe exact price of one prospective booking: subtotal, cleanup, groceries, travel and waiter fees, add-ons, voucher discount, the 10% service fee and the total. Saves nothing, holds no date, charges nobody — it answers "how much?". reserve_booking is what books. Call it before every reservation, and again after ANY change to the chef, package, guest count, add-ons, cleanup, groceries or voucher. Never restate an earlier total and never compute one yourself: fees are not proportional to guest count. Report the returned numbers exactly and get the customer's agreement to the total before start_booking. No customer address is taken by design: pricing is anchored to the chef's own city, so travel is normally 0 and reserve produces the same total. An unusable voucher_code is ignored rather than failing — check voucher_rejected and say so rather than implying a discount.
reserve_booking
ChatGPTCreate the real reservation and return the payment link. The only tool that books anything. Requires the draft_id from start_booking and a service_datetime_utc copied from get_chef_availability's slots_utc. Read the address, date, time, guest count and quoted total back to the customer and get an explicit yes first. The booking is created "awaiting payment": the chef sees it, but the date is only held until the customer pays at payment_url, by card or Pix, within 72 hours — after that it is released. Always show payment_url and the deadline. You cannot take payment here: never ask for card numbers, CPF or Pix details. On an error nothing was booked, and the message says what to fix. For a slot conflict, re-run get_chef_availability and re-offer rather than retrying the same time. Success is not proof this call created the booking: a draft already reserved — including by a duplicate call racing this one — returns the existing reservation instead of a second. Treat that as success and show the same payment_url. One draft is one booking; never call again "to be sure", and use start_booking for a genuinely new one.
search_chefs
ChatGPTFind private chefs who cook at the customer's home in one Brazilian city — the entry point for any request for a chef, private dinner, cooking class, event catering or meal prep (marmitas). Not for a chef you already hold a chef_id for: that is get_chef. Pass either city as the name the customer said, or a city_id returned by this tool or list_service_cities. Add state when city names are shared, or pass a natural form such as "Belém PA". City names are matched case- and accent-insensitively. If the city is still unknown or ambiguous the result carries city_candidates and no chefs; ask which one they meant and call again with its state. Use query for free text about food or occasion ("omakase", "vegan comfort food", "something for an anniversary"): it semantically matches chef profiles and beats the category filters whenever the customer describes a vibe. Use booking_type and cuisines only when they named that category. query overrides date. date keeps chefs whose weekly schedule covers that weekday; it does NOT mean a slot is free. Only get_chef_availability answers that. Returns a ranked list with rating, cuisines, services and a starting price. No menus, no totals, nothing reserved. Next: get_chef.
start_booking
ChatGPTCreate and prefill a myChef booking lead with the chosen chef, package, guest count and customer contact details. Returns the draft_id that reserve_booking requires, plus a browser link. Valid 7 days. Call it only once the customer has picked a chef and package, seen a real total from quote_booking, and agreed to be contacted. Consent is an LGPD requirement, not a formality — these details reach a real person by email and WhatsApp. BEFORE calling, tell the customer in your own words that their name, email and phone go to myChef, that myChef will email them a link to finish this booking and may follow up by email and WhatsApp, and that the privacy policy is https://mychef.com.br/pt/privacy-policy/. Then ask. Set contact_consent true only after they have actually agreed, in this conversation: earlier enthusiasm is not consent, and neither is silence. If they decline, do not call this tool — give them the chef's profile_url and stop. Send the details exactly as given; a mistyped email means the payment link never arrives. THIS TOOL DOES NOT CREATE A BOOKING: never tell the customer a booking or reservation was created. After success, continue by obtaining a real availability slot and service address, confirm them, then call reserve_booking. Calling again for the same chef and package reuses the existing lead.