Skip to main content
Glama

Kompare travel search

by io.kompare
OverviewDiscussionsAdmin

Find trips in plain words

find_trips
Read-onlyIdempotent

The quickest way to search: describe the trip in plain words and get bookable trips back in one call.

travelType, one of:

  • ski: ski and snowboard holidays

  • golf: golf holidays

  • surf: surf camps and holidays

  • diving: diving holidays

  • hiking: hiking and walking holidays

  • charter: package holidays: sun and beach trips with flight and hotel

  • cycling: cycling holidays

  • football: football trips: a match ticket with travel and hotel

  • carrental: car rental

  • f1: Formula 1 race trips

  • running: running races abroad, marathons and the like

  • americanfootball: NFL game trips

  • yoga: yoga retreats

  • triathlon: triathlon races and training camps

  • cruise: cruises

  • coach: coach (bus) tours

  • holidayhome: holiday homes and cottages

  • roundtrip: round trips and guided tours through several places

  • citybreak: city breaks

  • dance: dance holidays

places: destinations, ski areas, regions or countries in plain words, English or Danish ("Ischgl", "Østrig", "Costa del Sol"). Leave it out for anywhere. When: startFrom/startTo (the window the trip starts in) or months. Party: adults and children, since prices depend on them. Optional: durationDays, maxPricePerPerson, sort (best, cheapest, soonest), limit.

Response: { understood, ...{ total, accommodationCount, offset, results: [{ name, country, destination, stars, guestRating, tripsAvailable, trips: [{ start, end, durationDays, adults, children, price, pricePerPerson, currency, priceBeforeDiscount, transport, meals, unit, seller, bookingUrl }] }] } }

  • understood says how the request was read: the places searched, placesNotFound and placesAmbiguous. When a place was not found or is ambiguous, tell the user instead of presenting other trips as theirs.

  • price is the whole party's price; pricePerPerson divides it. Quote them as given, in currency — never convert or round them into a different claim.

  • trips holds the first few dates in sort order; tripsAvailable says how many more exist. Page with offset (it counts accommodations).

  • seller is the travel agency that sells the trip. bookingUrl opens that trip on the seller's site — give it to the user as the way to book. It is null when the seller can only be compared, not booked, through Kompare.

  • start/end are the trip's own first and last day. When nothing matches, the response holds alternatives (counts with one filter removed) to suggest what to relax. When no place matched at all, it holds a message and nothing was searched.

For a filter this tool lacks (meal plan, stars, transport, ski pass, distance to the lift, ...) use search_listings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNobest = Kompare’s ranking, cheapest = lowest price per person, soonest = earliest start. Kompare’s ranking weighs the price against similar trips, hotel stars, guest ratings, how well the trip fits the party and the commission the travel agency pays Kompare. Agencies with a commission agreement always rank above those without.best
limitNo
adultsNo
marketNodk
monthsNoMonths the trip may start in, YYYY-MM. Use instead of startFrom/startTo for "in February".
offsetNo
placesNoWhere, in plain words, English or Danish: a destination, ski area, region or country ("Ischgl", "Østrig", "Costa del Sol"). Leave out for anywhere.
startToNoLatest day the trip may start, YYYY-MM-DD.
childrenNo
startFromNoEarliest day the trip may start, YYYY-MM-DD.
travelTypeYesThe kind of trip. See the tool description.
durationDaysNoTrip lengths in days that fit, e.g. [7, 8] for a week.
maxPricePerPersonNoHighest price per person, in the market currency (DKK).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sort / description
      Previous value: -"best = Kompare’s recommendation, cheapest = lowest price per person, soonest = earliest start."New value: +"best = Kompare’s ranking, cheapest = lowest price per person, soonest = earliest start. Kompare’s ranking weighs the price against similar trips, hotel stars, guest ratings, how well the trip fits the party and the commission the travel agency pays Kompare. Agencies with a commission agreement always rank above those without."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial behavior beyond them: the full response shape, the meaning of 'understood' and the instruction to report placesNotFound/placesAmbiguous rather than substituting trips, pagination via offset, and that bookingUrl is null when a seller can only be compared. These are operational facts an agent cannot get from the annotations.

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

Conciseness4/5

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

Front-loaded with the one-line purpose, then parameters, then response, then fallback routing — a sensible order. It is long, but most of the bulk is the 20-value travelType reference and the dense response-shape line, both of which carry information the schema does not.

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?

There is no output schema, so the description must carry return semantics, and it does: field-by-field meaning, price vs pricePerPerson, the never-convert-the-currency rule, seller/bookingUrl handling, and the no-match alternatives path. For a 13-parameter tool with no output schema this is complete.

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

Parameters5/5

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

Schema coverage is 62%, and the description more than compensates: it enumerates all 20 travelType values (the schema explicitly defers to it with 'See the tool description'), explains places as English/Danish plain words with leave-out-for-anywhere semantics, distinguishes startFrom/startTo from months, and ties adults/children to pricing. Only 'market' is left unexplained.

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?

Opens with a specific verb+resource+mechanism: describe a trip in plain words and get bookable trips back in one call. It is clearly separable from search_listings, which is named as the tool for filters this one lacks, so an agent can route between the two without opening a schema.

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

Usage Guidelines4/5

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

States an explicit when-not with an alternative: 'For a filter this tool lacks (meal plan, stars, transport, ski pass, distance to the lift, ...) use search_listings.' That is strong routing. It gives no guidance, however, on how this relates to the other two siblings, get_facets and search_init, leaving part of the decision to inference.

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

All Kompare travel search toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources