Ratiba

Create a new client record. Search first with search_clients to avoid duplicates. Returns the new client id — pass it as `clientId` when creating a proposal for them.

create_client

Create a complete client-facing proposal in Ratiba. Search clients, accommodations, destinations, images, and pricing options before calling it. Accommodation and destination fields require real catalog ids, and room types must match the selected accommodation. For `useAutoPricing: true`, call get_pricing_options and select the applicable `vehicleId`, `vehicleCount`, `guideId`, pickup/drop-off transfer-rate ids, and `markupPct`; omit markupPct only when the organization's displayed default/tier should apply. Pass a YYYY-MM-DD `startDate` for real seasonal rates. The result includes `pricingReady` and `pricingIssues`; never call an auto-priced quote send-ready while pricingReady is false. Returns canonical `shareUrl`/`editUrl`; never construct them. Call get_proposal afterward to verify persisted client, itinerary, pricing, imagery, and theme. Translate only after the content is final.

create_proposal

Get full details (description, room types, amenities, images) for one accommodation by id.

get_accommodation

Get the full details of one proposal by id, including its day-by-day itinerary and pricing. For an auto-priced proposal (`useAutoPricing: true`), also includes a freshly-computed `pricingSummary` (cost by category, markup, sell total), plus `pricingReady` and actionable `pricingIssues`.

get_proposal

Return this organization's selectable vehicle, guide, and pickup/drop-off transfer rates, plus its default markup and group-size markup tiers. Call this before creating or updating an auto-priced proposal. Use only ids returned here; omitted markupPct uses the displayed organization default or tier.

get_pricing_options

List client proposals (quotes/sales documents) in the connected Ratiba account, optionally filtered by status or search text.

list_proposals

Set a proposal's active language back to English, undoing translate_proposal.

reset_proposal_language

Search existing accommodations (lodges/camps/hotels) to find valid ids for use as `accommodation` on a proposal day. Search by name, or filter by country (accommodations have no destination/park field, only a country and coordinates — use judgment, or cross-check `latitude`/`longitude` against the day's destination, when narrowing beyond country). Always search before guessing an id.

search_accommodations

Search existing clients by name. Use this before create_client to avoid creating a duplicate — if the client already exists, reuse their id as `clientId` on create_proposal/update_proposal.

search_clients

Search the destination catalog (national parks, reserves, cities, islands and landmarks) for the id to pass as a day's `destination`. That id is what puts the day on the client-facing map, and for a fee-bearing park it is also what applies park fees under `useAutoPricing`, so look the destination up here rather than relying on the written `destinationName` — beware near-namesakes such as "Arusha City" and "Arusha National Park", which are different places with different fees. Results without coordinates cannot be drawn on the map. An empty query returns a sample of the catalog.

search_destinations