Skip to main content
Glama

Honee – cruise · honeefy

Find bookable cruises

find_cruises
Read-onlyIdempotent

Searches the provider's LIVE, bookable sea and river cruise offers for a destination, a travel period and a travel party. Use it whenever the user asks about cruise offers, prices, dates or availability, wants to see, compare or book cruises: prices and availability change several times a day and this tool has the live availability for the traveller's party. Requires adults, period (or from_date/to_date) and destination — if any is missing, unusable or not a region this provider can search, the result lists a question for it and no search runs; ask the user, then call again with the same handle. For river cruises pass cruise_type='river' (a river name such as 'Danube' is recognised too). Sea cruises are shown WITHOUT a flight package by default; pass flight='with' to get the flight packages instead. Returns a summary plus up to 10 offers with cruise_id, ship, cruise line, dates, nights, price with currency (per person; for families the cabin total for the whole party where the provider computes it) and the booking link. Where the provider supports it, availability is checked LIVE for the top offers and each says whether it is confirmed; sold-out ones are removed. The list is a SAMPLE of the provider's matches: the result says how many exist and which cruise lines have sailings -- never conclude that a line is not offered because it is not listed; pass cruise_line to look for it. It does NOT show anything to the user, book, hold or price cabins, know availability beyond what it returns, or search by price alone. If you are recommending cruises, call show_offers ONCE afterward with the cruise_id values of your recommendation (3-5). Never invent offers that are not in the result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many offers to return as data (3-10, default 10). The result also carries `total` and `links.all` (every match on the provider's search page).
portsNoPorts, islands or countries that must ALL be on the route (start, a stop or the end), e.g. ['Barbados', 'St. Lucia'] or the port cities ['Bridgetown', 'Castries'] -- an island/country entry matches any of its ports on the route. Names are matched in English; a translated name may find nothing, try the English or the specific port city instead.
adultsNoNumber of adults travelling.
flightNo'without' (default): cruise only. 'with': the provider's flight packages.
handleNoConsultation handle returned by a previous call (structuredContent.handle). Pass it on every call so wishes are remembered; omit it on the very first call.
periodNoTravel period as free text, e.g. 'summer 2027', 'October 2027', '2027-06-01 to 2027-06-30'.
to_dateNoLatest departure, ISO date. Alternative to period.
languageNoLanguage of the answer. Defaults to the provider's language.
from_dateNoEarliest departure, ISO date. Alternative to period.
nights_maxNoMaximum nights. Only if the user names a trip length; below 4 nights asks for short cruises first.
nights_minNoMinimum nights. Only if the user names a trip length.
cruise_lineNoCruise line(s) by name, e.g. 'MSC' or 'MSC, AIDA' (comma-separated). The search is filtered AT THE PROVIDER, so use it to look for a line the default list does not show.
cruise_typeNo'ocean': sea cruises. 'river': river cruises (Danube, Rhine, Moselle, Nile, ...). Omit it to derive it from the destination.
destinationNoRegion, country, sea or river in any language, e.g. 'Mediterranean', 'Norwegian fjords', 'Caribbean', 'Danube'. For a river cruise on any river pass 'river cruise'.
children_agesNoAge of each child at travel time. A child without an age is not searched for.
departure_portNoA single port that must be on the route (start, stop or end), e.g. 'Barcelona'. For several required ports use `ports` instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only cover safety (readOnly/idempotent), but the description adds rich behavioral context: prices change several times a day, requiring adults/period/destination or the call fails with a question, handle reuse to remember wishes, river vs sea handling, sample-not-exhaustive results, live availability checks with sold-out removal. These are non-obvious behaviors an agent must know to use the tool correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and usage, but the description is a very long run-on paragraph with many clauses. It packs in a lot of useful behavior but could be structured better with breaks or bullet points for readability. Information density is high, but not optimally organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description fully explains the return shape (summary plus up to 10 offers with cruise_id, ship, line, dates, nights, price, booking link), how total matches are indicated, and the requirement to follow up with show_offers. Everything an agent needs to call and interpret results is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all 16 parameters thoroughly. The description adds cross-parameter semantics: 'cruise_type=river' recognition of river names, 'flight=with' toggling flight packages, handle reuse across calls, cruise_line used to filter at provider. It doesn't repeat the schema mechanically but adds contextual meaning exceeding baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Searches the provider's LIVE, bookable sea and river cruise offers') and names the exact required inputs. It also explicitly lists what the tool is NOT ('does NOT show anything to the user, book, hold or price cabins... or search by price alone'), drawing sharp boundaries against siblings like show_offers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use it ('whenever the user asks about cruise offers, prices, dates or availability, wants to see, compare or book cruises'), how it routes to a sibling ('call show_offers ONCE afterward with the cruise_id values of your recommendation'), and lists exclusions. This is comprehensive routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources