Kratons, boutique DMC: bespoke trips in Spain, Portugal, Morocco. Facts, catalog, reviews, requests.
Scored across 8 tools
The tools split cleanly around discovery (destinations, experiences, itineraries, reviews) and the proposal workflow (request, status, how-to). However, how_to_request_a_proposal and get_company_facts both cover pricing policy and how to request a proposal, so an agent could reasonably pick either for those questions.
Most tools follow a clear snake_case verb_noun pattern (get_*, list_*, search_*, request_*). The one outlier is how_to_request_a_proposal, which describes a topic rather than an action, though it is still stylistically consistent.
Eight tools is well-scoped for a public-facing company info and proposal-request service. Each tool represents a meaningful query or workflow step, with no obvious bloat.
The set covers the full public journey: learn about the company, browse destinations/experiences/itineraries, see reviews, request a proposal, and track its status. The proposal lifecycle has both submit and status lookup, leaving no major dead end.
Who Kratons is: legal identity, address, contact channels, countries served, languages, services, pricing policy and how to request a proposal. Read-only.
Inputs: no named parameters. Returns: api, web, iata, brand, +14 more
Where a submitted proposal request stands (received, being prepared, proposal sent, confirmed, closed), looked up by the reference returned when it was submitted. Returns the stage, dates and the reply commitment; no personal data.
Inputs: reference (required). Returns: status, nextStep, reference, receivedAt, +3 more
Aggregate rating (1–5) and the newest traveller reviews of Kratons from Zicasso and Google, each attributed to the platform that published it, with a link to read them all. A source that cannot be read is listed as unavailable — never invented.
Inputs: limit. Returns: note, reviews, sources, bestRating, +3 more
The checklist a traveller or agent should send to Kratons to receive a bespoke proposal, the pricing policy, and how a human advisor follows up. Read-only.
Inputs: no named parameters. Returns: how, guide, contact, checklist, +3 more
Countries and cities where Kratons currently offers tours or tickets, with counts. Read-only.
Inputs: no named parameters. Returns: countries, generatedAt
Published sample itineraries Kratons operates, as { itineraries: [...] } (name, destination, duration, category, summary, day-by-day outline) to start a conversation from. Never prices or suppliers — every trip is quoted as one package price by a human advisor.
Inputs: q, limit, country. Returns: itineraries
Submit a structured proposal request to Kratons on behalf of a traveller or a travel agent: contact, destinations within Spain/Portugal/Morocco, dates, travellers, total budget, interests. Returns a reference. A human advisor replies by e-mail — there is no automatic booking, no online checkout and no price list. Send idempotencyKey to retry safely.
Inputs: trip (required), contact (required), utm, source, +3 more. Returns: missing, duplicate, reference, receivedAt, +3 more
Tours and tickets Kratons operates, filtered by country, city and free text. Returns { experiences: [...] } with name, type, city, country, category, duration, free-cancellation flag and a summary — never prices or suppliers (Kratons quotes one package price per trip).
Inputs: q, city, limit, country. Returns: experiences
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Read-only 1-3 day trips in PT/Europe by train, boat, plane and on foot. Not an agency.
Read-only MCP for Sparkling Tracks European tours: packages, itineraries, pricing, contacts.
Plan, quote & book the Camino de Santiago: routes, stages, live hotels, one package price, FAQ.
Multilingual travel guides, gear picks and booking links for AI travel agents.
Add one secure layer between your agents and this server.
