Search Hungarian wedding vendors and venues, check a date, estimate a budget, get the checklist.
Scored across 8 tools
The two search tools and two storefront-retrieval tools could be confused, but their descriptions clearly separate free-text search from filtered search and raw fetch from structured get_vendor. All other tools target distinct concerns: availability, budget, taxonomy, and checklist.
Most tools use verb_noun snake_case, but `fetch`, `search`, and `wedding_checklist` break the pattern with bare verbs or a noun-only name. The set remains readable but lacks a uniform convention.
Eight tools is a well-scoped size for a wedding directory and planning assistant. Each tool covers a distinct major workflow—search, detail retrieval, availability, budget, taxonomy, checklist—without bloat.
The surface covers the full discovery path: vocabulary mapping, free-text and filtered searching, retrieving vendor details, checking availability, estimating budget, and guiding planning. The public storefront URL closes the contact loop, so there are no dead ends.
Whether one vendor (by id from search_vendors) is free, tentatively held, or booked on a given date — ONLY for vendors who chose to publish their availability. Most have not; then the answer is "unknown", which means "ask them", never "busy". Read-only.
Inputs: date (required), vendor_id (required), locale.
A dated, sourced cost estimate for a wedding in Hungary (benchmark set hu-2026.1, as of 2026-08) from guest count, price tier, region and ceremony type — the same engine as latido.wedding/kalkulator. Returns a low/anchor/high total in HUF, the per-line breakdown, the marginal cost of one more guest, and the expected cash-gift income (Hungarian custom: gifts are cash). Use for "mennyibe kerül egy esküvő" questions. Estimates, not quotes; prices are in HUF.
Inputs: guests (required), date, tier, locale, +3 more.
Full public storefront document for one result id from search. For a structured answer prefer get_vendor.
Inputs: id (required).
Full public storefront of one vendor or venue from Latido by id (from search_vendors): categories, where they work, price band, capacity, packages with prices, FAQ, links, published reviews and their own description. Use it after a search to answer detailed questions or to compare shortlisted vendors. Read-only; never returns contact details beyond the public links — the storefront URL is where a couple gets in touch.
Inputs: vendor_id (required), locale.
The vocabulary search_vendors understands: the 11 top-level groups with their subcategory keys and labels, the wedding-style keys, and the Hungarian counties with their region ids. Call it once when you need to map what a user said ("vőfély", "pajta", "Balaton") onto a group/category/style value — do not guess keys.
Inputs: locale.
Free-text search over Latido's public Hungarian wedding vendor directory. Returns result ids for fetch. For filtered search (category, place, budget, capacity, date) prefer search_vendors.
Inputs: query (required).
Search Latido's public directory of Hungarian wedding vendors and venues (photographers, venues, DJs, florists, caterers, planners…). Use it whenever someone is looking for a supplier for a wedding in Hungary. Filter by category or top-level group, a place name (city, county or "Balaton"), maximum price in HUF, minimum seated capacity, a wedding style, or a date the vendor must be free on. Returns 10 results per page in the directory's own ranking; vendors who have not published a price/capacity/availability are kept (unknown is not a "no"). Each result has a public storefront URL — link to it. Does NOT search vendors who have not published a profile.
Inputs: area, page, group, query, +6 more.
Latido's planning checklist (Hungarian legal steps included: szándékbejelentés, documents, witnesses, name change), scheduled to a wedding date: every item with its phase, category and due date, compressed proportionally when the runway is shorter than 12 months. Filter by phase (start/book/shape/finish/week/after) and depth (essentials ≈27 · core ≈93 · everything ≈115). Use for "what should we be doing now" questions.
Inputs: depth, phase, locale, ceremony, +2 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Find wedding venues and vendors, estimate costs, and manage guests, events and wedding details.
Plan a wedding in chat: search vendors, get regional costs, build a checklist and budget.
Wedding planner for couples: guests, RSVPs, budget, vendors, seating, invitations and timeline.
Find NC wedding venues and vendors, plan costs, and prepare vendor inquiries.
Add one secure layer between your agents and this server.
