nyna — AI wedding planner

[Sign-in required] Appends up to 100 named guests to the guest list in one write — costs no credits and returns the names added, the names skipped as duplicates and the new total. Existing guests are left untouched, the whole batch is validated before anything is written, and a member whose role only proposes guests gets proposals recorded for the couple instead of additions.

[Sign-in required] Reads the couple’s checklist — costs no credits and returns each item with its id, title, status, due date and category, plus the totals (all, done, to do) so nothing has to be counted.

[Sign-in required] Reads the connected account’s credit balance — costs no credits and returns the balance, the price of each metered action in the nyna app, and the list of MCP tools that spend credits (none today).

[Sign-in required] Reads the wedding-day plan — costs no credits and returns the run sheet, vendor coordination status, guest figures, readiness score and flags, and the days remaining; what has not been filled in is named rather than guessed at.

[Sign-in required] Reads the guest list — costs no credits and returns each guest with RSVP status, side and table, plus head-count totals by status so nothing has to be tallied.

[Free] Reads one provider by the id search_providers returns — costs no credits and returns at least what the search result held: name, address, city, category, Google rating and review count (from nyna’s index, or live from Google Places when the index has none and today’s budget allows), whether the listing is claimed, and — for a claimed listing — the owner’s description, services, website and phone, plus the nyna page. Prices and availability are not held.

[Partner] Reads the enquiries couples sent through the connected provider’s nyna listing, newest first — costs no credits and returns each enquiry (sender name, message, wedding date, status) plus totals by status so the pipeline needs no counting.

[Partner] Reads the connected provider account’s own listing — costs no credits and returns an `editable` half (exactly the fields update_provider_profile accepts, under the same names: description, services, price range, website, Instagram, phone, city) and a `derived` half nyna decides (business name, category, plan, verification, featuring, status).

[Partner] Reads the connected provider’s listing performance over a chosen window — costs no credits and returns views, enquiries and conversion for the window actually measured, naming any figure nyna does not collect rather than returning a null nobody can interpret.

[Sign-in required] Reads the connected account’s wedding — costs no credits and returns the date, venue, budget, guest count and theme in a `writable` half (exactly the fields update_wedding accepts, under the same names) plus a `derived` half with days remaining, guest totals and checklist progress. A member’s role decides what comes back: the budget is omitted for a role without budget:view.

[Free] Lists the featured cities — the ones with a nyna directory page — optionally filtered by region — costs no credits and returns city slugs, country, region and page. This is not the limit of coverage: search_providers takes any city, town or place name in the world as `city` ("Gardanne", "Bouc-Bel-Air 13320", "Istanbul"), and geocodes it once; the featured cities are simply the ones with a browsable page.

[Free] Lists the gift categories and the countries the gift catalogue is localised for — costs no credits and returns the closed sets of slugs that search_gift_ideas takes as `category` and `country`.

[Free] Lists the kinds of wedding provider nyna indexes (venues, caterers, photographers…) — costs no credits and returns the closed set of category slugs that search_providers takes as `category`, each with its English and French name and its nyna page. Any `category` value outside this set is refused with the valid list.

[Sign-in required] Parses a pasted guest list — one per line or comma-separated, with or without emails and phones — into structured guests with detected roles — costs no credits (rate-limited to 10 a minute) and returns them for review; add_guests is the separate call that saves the ones kept.

[Free] Quotes a tool before it is called — costs no credits and returns the credits a successful call spends (0 for every tool today), the scopes it needs, the rate limits it runs under, its annotations and whether it accepts an idempotency_key. Nothing is charged on failure for any tool, so there is nothing to refund.

[Free] Searches the wedding-gift ideas couples added to their nyna registries, by category, country, title and price — costs no credits and returns up to 50 ideas with price, currency, image and a store link (some links carry an affiliate tag that never changes the ordering), plus `catalogue_size`, how many ideas the catalogue holds for that country: it is a grown catalogue, not a store feed, and is thin outside France. Slugs are the ones list_gift_categories returns; any other value is refused with the valid set.

[Free] Searches wedding providers — venues, caterers, photographers, florists and more — around any city or place in the world, by category and free text — costs no credits and returns up to 50 providers with address, distance from the city centre, Google rating, review count and nyna page, plus how old the index is. `city` is any city, town or place name ("Aix-en-Provence", "Gardanne", "Bouc-Bel-Air 13320", "Istanbul"), resolved once and cached; only a name Google cannot place is refused. `category` is a slug from list_provider_categories; without one, the free text `q` is searched across every category. `q` matches names, specialities and cuisines ("halal", "turkish", "bastide", "château"): it is matched against indexed names, claimed listings (description, services) and the live Google search. `radius_km` (5–100, default 25) bounds the results; `sort` is relevance (claimed listings first, then nyna’s index, then live results), rating or reviews.

[Sign-in required] Marks one checklist item done or not done — costs no credits and returns the item with its previous and new state. The item is addressed by the `id` get_checklist returns (stable even when the list changes) or by its `index` for items without an id; an item that does not exist is refused rather than created.

[Sign-in required] Writes a reviewed timeline to the wedding as the day-of run sheet, replacing the one there — costs no credits and returns the number of events saved and the number replaced. Times are 24h HH:MM in chronological order; an out-of-order sheet is refused before anything is written.

[Sign-in required] Generates a 10–15 event wedding-day timeline in 24h time, shaped by the connected account’s venue, ceremony type and guest count — costs no credits (rate-limited to 10 generations a minute) and returns the schedule for review; set_run_sheet is the separate call that writes one to the wedding.

[Sign-in required] Generates a wedding menu — cocktail, starters, mains, desserts, drinks, cake and a children’s menu — sized to the connected account’s guest count, theme and budget — costs no credits (rate-limited to 10 generations a minute) and returns the menu for review; nothing is written to the wedding.

[Partner] Updates the connected provider’s listing — description, services, price range, website, Instagram, phone, city (any city in the world, as a display name) — as a merge patch — costs no credits and returns the fields changed. Omitted fields are left alone; plan, verification, featuring and status are refused by name because they are sold or earned, never self-assigned.

[Sign-in required] Updates the wedding’s details — date, venue, budget, guest count, theme, notes — as a merge patch — costs no credits and returns the fields changed and whether the wedding was created by this call. Omitted fields are left alone; a value that contradicts what the couple said in nyna’s chat comes back as `conflict` and is written only when sent again within 15 minutes; share-control fields are refused by name, never silently dropped.