Karta

Invent a Docker-style cat name (adjective Scientist). Present the returned name playfully as the user’s new Karta house-cat mascot — one short witty line (optional 🐱); never rename what the tool returned.

cat_name

Get the catalog for one specific stay — use when a user asks about a particular hotel or apartment ("tell me about this place", "what amenities does it have"). Funnel step 2: catalog for one listing (what the place is) — description, photos, amenities, neighborhood, check-in/out hours, house rules, highlights. Not live from-prices and not room rates for dates (that is listing_rates). Pass url: listing_page_url from stays_search or listing_url from a previous listing_details. Returns listing_url (property page self-link).

listing_details

Use when a user wants rooms, prices, board or cancellation for one stay. Funnel step: listing-page rates — live rooms→rates for one listing × dates/guests. Shape: property → rooms[] → rates[] with summary (board · free cancel until / non-refundable), price, board, compact cancellation (refundability + refundable_until; no raw policy dump). Pass url (listing_page_url or listing_url); optional arrival/departure/adults/child_ages override URL query. Not catalog (listing_details). Compare rates in chat; to book, open listing_page_url in a browser.

listing_rates

Extended Karta MCP playbook: funnel meaning, how to / how not to, when to use location vs bbox, handoffs between tools. Call when unsure which Karta tool to use next (no arguments).

mcp_guide

Use for accommodation requests — hotels, apartments, aparthotels, hostels, B&Bs ("hotels in Barcelona", "where to stay near the beach", "stays for 2 adults and a child"). Searches the Karta stays API by city/region/landmark and returns live from-prices aggregated across multiple suppliers, each with a direct Karta listing page. Funnel step 1: many places for dates/guests. Required: direction, dates (arrival/departure), pax (adults); optional pax.child_ages. Where: direction.text and/or direction.bbox (when both set, bbox wins for geometry; text stays the label). Free-text resolves to a search box — "City, Country" retries the bare city on a miss. When the text does not resolve to a search box but the place is known, the result carries direction.candidates (name/type/bbox) and status "choose_direction" — pick one candidate and search again with its bbox. A search box wider than ~10_000 km per side (near-hemisphere) is not searched: the result carries status "bbox_too_large" with the limit and measured km, and direction.candidates is pre-filtered to places that fit the limit — pick one and search again. Province- and country-sized boxes are fine. Only a place that cannot be resolved is an error. Returns stays[] short cards with indicative from-prices (nightly_from / total_from) — not a full room-rate list and not full catalog. Each card carries listing.photos (absolute, ready-to-show image URLs) and listing_page_url — pass the URL unchanged to listing_details / listing_rates (url) or open in browser. Next: listing_details (catalog). Depth: scan "short" (default, first batch, fast) or "full" (all batches, like the web UI). limit caps the number of stays returned (0 or omit = all). When the host renders this tool's UI, the results appear on their own — do not repeat them as a markdown table, list or raw JSON, and do not retype card fields (title, photo, price, address). Add at most one short sentence (area, count, price range) and leave the cards to the UI. When the host renders no UI, answer with a short plain list (name — from-price — listing_page_url), never a markdown table and never the raw JSON. Then listing_rates (rooms→rates). To book, open listing_page_url in a browser.

stays_search