Search VICATOO hotels by traveler needs, features, location, and landmarks with factual evidence.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Returns factual information about VICATOO the company: who VICATOO is, the "Truth Before You Book" value proposition and benefits, and trust credentials (legal entity, TRUE/CCRA accreditation, D-U-N-S number, registered address). Call this whenever the guest asks who VICATOO is, why they should trust VICATOO, what VICATOO offers or how it is different, or anything about the company or brand — so you answer from grounded facts, never invented ones.
This tool takes no arguments.
Returns factual information about VICATOO the company: who VICATOO is, the "Truth Before You Book" value proposition and benefits, and trust credentials (legal entity, TRUE/CCRA accreditation, D-U-N-S number, registered address). Call this whenever the guest asks who VICATOO is, why they should trust VICATOO, what VICATOO offers or how it is different, or anything about the company or brand — so you answer from grounded facts, never invented ones.
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}Fetch live VICATOO rates for a hotel for the given check-in/check-out dates and occupancy. Returns up to `limit` rates with room name, price, meal type, bed type and cancellation policy. Booking itself always completes on vicatoo.com — to book, direct the guest to open the hotel page URL (the search_hotels card link already carries the dates and guests); never promise in-chat booking.
| Argument |
|---|
| Type |
|---|
| Description |
|---|
| view | string | Optional preferred view family (e.g. "bosphorus", "sea", "garden", "city", "pool"). When the guest cares about a specific view, pass it so matching-view rates are floated to the top instead of the default cheapest-first ordering. |
| limit | integer | |
| rooms | integer | |
| adults | integer | |
| check_in* | string | |
| currency | string | 3-letter ISO currency for the rate prices. Defaults to USD so rates match the search-result prices; pass the same currency the guest saw in search. |
| hotel_id* | any | VICATOO hotel id — numeric hid or slug (same as get_hotel_details). |
| check_out* | string | |
| residency | string | ISO 3166-1 alpha-2 code of the country the guest LIVES in - the supplier prices by it, and the hotel page link carries it. If the guest has not said where they live, leave it out and ask them first ("which country do you live in?", in their own language). Never assume US or any other country. |
| children_ages | array | |
| room_type_filter | string | Optional case-insensitive substring filter on room_name. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"hotel_id",
"check_in",
"check_out"
],
"properties": {
"view": {
"type": "string",
"maxLength": 20,
"description": "Optional preferred view family (e.g. \"bosphorus\", \"sea\", \"garden\", \"city\", \"pool\"). When the guest cares about a specific view, pass it so matching-view rates are floated to the top instead of the default cheapest-first ordering."
},
"limit": {
"type": "integer",
"default": 10,
"maximum": 30,
"minimum": 1
},
"rooms": {
"type": "integer",
"default": 1,
"maximum": 4,
"minimum": 1
},
"adults": {
"type": "integer",
"default": 2,
"maximum": 8,
"minimum": 1
},
"check_in": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"currency": {
"type": "string",
"default": "USD",
"maxLength": 3,
"minLength": 3,
"description": "3-letter ISO currency for the rate prices. Defaults to USD so rates match the search-result prices; pass the same currency the guest saw in search."
},
"hotel_id": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
},
{
"type": "string",
"maxLength": 120,
"minLength": 1
}
],
"description": "VICATOO hotel id — numeric hid or slug (same as get_hotel_details)."
},
"check_out": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"residency": {
"type": "string",
"maxLength": 2,
"minLength": 2,
"description": "ISO 3166-1 alpha-2 code of the country the guest LIVES in - the supplier prices by it, and the hotel page link carries it. If the guest has not said where they live, leave it out and ask them first (\"which country do you live in?\", in their own language). Never assume US or any other country."
},
"children_ages": {
"type": "array",
"items": {
"type": "integer",
"maximum": 17,
"minimum": 0
},
"default": [],
"maxItems": 6
},
"room_type_filter": {
"type": "string",
"maxLength": 60,
"minLength": 1,
"description": "Optional case-insensitive substring filter on room_name."
}
}
}Fetch full details for a single hotel by its VICATOO hotel_id (numeric hid, the hotel_id search_hotels returns, or the slug). Returns name, star rating, REAL guest rating (score/10 + review count — cite it, and call get_hotel_reviews for guest pros/cons before strongly recommending), what the hotel is known for (vibe_tags), location, check-in/out times, headline amenities, images, a description, AND the available rooms cheapest-first — each with photos, a live price (total for the stay and per night), size, view, bed type, meal plan and cancellation. PRICES ARE FOR A STAY: pass check_in, check_out, adults and children_ages (the same values as the guest's search_hotels call) so the prices are for their stay. Without dates the prices are APPROXIMATE, for a default stay the reply names (prices_for.approximate = true) — say so to the guest. When has_video is true, offer the real room-tour video via get_room_video with the returned reel_id.
| Argument | Type | Description |
|---|---|---|
| lang | string | 2-letter language code for content (en, ar, de, fr, es, ru, etc.). |
| view | string | Optional preferred view family (e.g. "bosphorus", "sea", "garden", "city", "pool"). When the guest arrived from a view-constrained search, pass it so rooms with that view are floated to the top instead of the default cheapest-first ordering. |
| adults | integer | |
| check_in | string | YYYY-MM-DD. Pass the same stay the guest searched, so the room prices are for it. |
| currency | string | 3-letter ISO currency for room prices. Defaults to USD so hotel details match the search-result prices; pass the same currency the guest saw in search. |
| hotel_id* | any | VICATOO hotel id — either the numeric hid (e.g., 7476954) or the slug (e.g., "bentley-hotel-bosphorus-7476954"). |
| check_out | string | YYYY-MM-DD. |
| residency | string | ISO 3166-1 alpha-2 code of the country the guest LIVES in - the supplier prices by it, and the hotel page link carries it. If the guest has not said where they live, leave it out and ask them first ("which country do you live in?", in their own language). Never assume US or any other country. |
| children_ages | array |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"hotel_id"
],
"properties": {
"lang": {
"type": "string",
"default": "en",
"maxLength": 2,
"minLength": 2,
"description": "2-letter language code for content (en, ar, de, fr, es, ru, etc.)."
},
"view": {
"type": "string",
"maxLength": 20,
"description": "Optional preferred view family (e.g. \"bosphorus\", \"sea\", \"garden\", \"city\", \"pool\"). When the guest arrived from a view-constrained search, pass it so rooms with that view are floated to the top instead of the default cheapest-first ordering."
},
"adults": {
"type": "integer",
"default": 2,
"maximum": 8,
"minimum": 1
},
"check_in": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "YYYY-MM-DD. Pass the same stay the guest searched, so the room prices are for it."
},
"currency": {
"type": "string",
"default": "USD",
"maxLength": 3,
"minLength": 3,
"description": "3-letter ISO currency for room prices. Defaults to USD so hotel details match the search-result prices; pass the same currency the guest saw in search."
},
"hotel_id": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
},
{
"type": "string",
"maxLength": 120,
"minLength": 1
}
],
"description": "VICATOO hotel id — either the numeric hid (e.g., 7476954) or the slug (e.g., \"bentley-hotel-bosphorus-7476954\")."
},
"check_out": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "YYYY-MM-DD."
},
"residency": {
"type": "string",
"maxLength": 2,
"minLength": 2,
"description": "ISO 3166-1 alpha-2 code of the country the guest LIVES in - the supplier prices by it, and the hotel page link carries it. If the guest has not said where they live, leave it out and ask them first (\"which country do you live in?\", in their own language). Never assume US or any other country."
},
"children_ages": {
"type": "array",
"items": {
"type": "integer",
"maximum": 17,
"minimum": 0
},
"default": [],
"maxItems": 6
}
}
}Fetch a hotel's guest reviews from VICATOO's own reviews: the guest rating (out of 10, with the number of reviews) and the written reviews (pros, cons, comments), from the same source, newest first. Paginate the written reviews with `cursor` and `limit`. When the hotel's reviews have no written comments, the reply says so — do not invent any.
| Argument | Type | Description |
|---|---|---|
| limit | integer | |
| cursor | integer | Offset into the written reviews (0-based). |
| hotel_id* | any | VICATOO hotel id — numeric hid, the hotel_id search_hotels returns, or the slug; all are resolved server-side. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"hotel_id"
],
"properties": {
"limit": {
"type": "integer",
"default": 12,
"maximum": 30,
"minimum": 1
},
"cursor": {
"type": "integer",
"default": 0,
"maximum": 9007199254740991,
"minimum": 0,
"description": "Offset into the written reviews (0-based)."
},
"hotel_id": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
},
{
"type": "string",
"maxLength": 120,
"minLength": 1
}
],
"description": "VICATOO hotel id — numeric hid, the hotel_id search_hotels returns, or the slug; all are resolved server-side."
}
}
}Returns VICATOO's real room-tour video for a hotel reel as a branded reel PAGE link on vicatoo.com (reel_url). The reel is a promotional public asset: share that page link with the guest freely — NEVER surface any raw video file URL. Includes hotel/room name and caption.
| Argument | Type | Description |
|---|---|---|
| reel_id* | any | Reel primary-key id (numeric). |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"reel_id"
],
"properties": {
"reel_id": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
},
{
"type": "string",
"pattern": "^\\d{1,9}$"
}
],
"description": "Reel primary-key id (numeric)."
}
}
}Search hotels by a descriptive natural-language query in Arabic or English. Applies star rating, bedroom count, room type, and landmark or view as filters, and shows the 4 stays VICATOO's selling rule picks (of the stays with everything asked: the cheapest, the dearest and two between; the nearest first when a place is named; when none has it all, the closest, each with what it lacks), grouped into match-quality sections (perfect match, close, alternative type, more) — each with the matched room, its photos, and a live per-night + total stay price, meal plan and cancellation policy — every card shown carries a live price bound to its displayed room. Use it for any hotel search; pass the user's full descriptive phrase as `query` (for example "5-star hotel in Paris" or "two-bedroom apartment with an Eiffel Tower view"). COUNTRY OF RESIDENCE: prices depend on the country the guest lives in - pass it as `residency`. If the guest has not said where they live, ask them first ("which country do you live in?", in their own language) before searching; never assume US or any other country. Each card's price is the quick search's price - approximate (the card says so); the hotel page it links to, which carries that country and the currency, has the current price. Call check_availability for booking-ready rates on a specific hotel. TIER MEANINGS (disclose when recommending): perfect = every stated constraint met; near = minor deviation; unit_swap = the requested unit type had no availability so a similar type is offered; wider/fallback = constraints relaxed. PRESENTATION (follow this when you talk about the results): you are VICATOO's travel concierge — always call the platform VICATOO, never name any supplier. Speak warmly and help the guest feel confident booking, but stay strictly truthful per 'Truth Before You Book': no invented urgency, no 'booked N times', no fake scarcity — only real signals. The real quality signals you may cite: review_score (out of 10) with review_count, and vibe_priority (what the hotel is known for, e.g. families/spa/luxury). For each hotel say in one line WHY it matches (tier, view, distance, what it is known for, rating), and briefly compare the top 2-3 so the guest can choose. Before strongly recommending one hotel, call get_hotel_reviews for real guest pros/cons. When a card has has_reel=true, offer VICATOO's real room-tour video via get_room_video with that card's reel_id. When the search includes children, mention each hotel's extra-bed note so families know whether a child bed is included before they open the page. NEVER render external/third-party maps (Google Maps widgets etc.) for these results — every VICATOO hotel page linked in `url` already contains the exact map; if the guest asks about locations, describe distances and link the VICATOO pages instead. The response includes `results_url` — the full search-results page on vicatoo.com with the same query and dates. ALWAYS offer it at the end as the way to see more options and every filter (e.g. "لمزيد من الخيارات" / "see all results on VICATOO"). Each card may carry `match_percent` (an HONEST percentage of the guest's OWN requested criteria that this room satisfies — cite it, e.g. "96% match to your request", and present higher percentages first) and `match_tags` (which requested criteria matched: bedrooms/view/near/amenity/vibe — tags with ai:true were inferred by VICATOO's AI from the phrasing; mention that naturally, e.g. "our AI also picked up you want somewhere quiet"). Never invent a percentage when match_percent is null.
| Argument | Type | Description |
|---|---|---|
| lang | string | The user's language as an ISO 639-1 code (e.g. 'ar', 'ru', 'de', 'fr', 'en') for localizing the result cards. Infer it from the conversation language. If omitted, it is detected from the query script. |
| query* | string | The full descriptive search phrase from the user (city + any room type, view, budget, star rating, bedroom count, or vibe cues). Pass exactly what the user typed — e.g. "5-star hotel in Paris" or "شقة غرفتين إطلالة على برج إيفل". The backend parses Arabic/English intent and applies stars / bedrooms / landmark as real constraints — do NOT pre-strip the phrase down to a city. |
| rooms | integer | |
| adults | integer | |
| check_in* | string | YYYY-MM-DD |
| check_out* | string | YYYY-MM-DD |
| residency | string | ISO 3166-1 alpha-2 code of the country the guest LIVES in - the supplier prices by it, and the hotel page link carries it. If the guest has not said where they live, leave it out and ask them first ("which country do you live in?", in their own language). Never assume US or any other country. |
| children_ages | array |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query",
"check_in",
"check_out"
],
"properties": {
"lang": {
"type": "string",
"description": "The user's language as an ISO 639-1 code (e.g. 'ar', 'ru', 'de', 'fr', 'en') for localizing the result cards. Infer it from the conversation language. If omitted, it is detected from the query script."
},
"query": {
"type": "string",
"maxLength": 200,
"minLength": 2,
"description": "The full descriptive search phrase from the user (city + any room type, view, budget, star rating, bedroom count, or vibe cues). Pass exactly what the user typed — e.g. \"5-star hotel in Paris\" or \"شقة غرفتين إطلالة على برج إيفل\". The backend parses Arabic/English intent and applies stars / bedrooms / landmark as real constraints — do NOT pre-strip the phrase down to a city."
},
"rooms": {
"type": "integer",
"default": 1,
"maximum": 4,
"minimum": 1
},
"adults": {
"type": "integer",
"default": 2,
"maximum": 8,
"minimum": 1
},
"check_in": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "YYYY-MM-DD"
},
"check_out": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "YYYY-MM-DD"
},
"residency": {
"type": "string",
"maxLength": 2,
"minLength": 2,
"description": "ISO 3166-1 alpha-2 code of the country the guest LIVES in - the supplier prices by it, and the hotel page link carries it. If the guest has not said where they live, leave it out and ask them first (\"which country do you live in?\", in their own language). Never assume US or any other country."
},
"children_ages": {
"type": "array",
"items": {
"type": "integer",
"maximum": 17,
"minimum": 0
},
"default": [],
"maxItems": 6
}
}
}