Skip to main content
Glama

KAYAK flight route overview between two city or airport

travel_kayak
Read-only

KAYAK flight route overview between two city or airport codes (e.g. LON to PAR): up to 20 recent round-trip deals KAYAK found (airline, departure/arrival airport, departure time, duration, price in USD), the route's lowest recent price and KAYAK's published route insights as question/answer text (typical price range, cheapest month, day and airline, delays, flights per week). From KAYAK's public route page; not a live date search. Related tools on this server, for a different need: travel_momondo when you need momondo flight prices from its public route page for two; travel_rome2rio when you need Rome2Rio ways to travel between two places: the headline. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "travel_kayak"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination IATA city or airport code, e.g. PAR, MIA
fromYesOrigin IATA city or airport code, e.g. LON, NYC, JFK
insightsNoInclude route insight answers: true (default) or false

Output Schema

NameRequiredDescriptionDefault
toNo
fromNo
countNo
dealsNo
routeNo
sourceNo
currencyNo
insightsNo
lowPriceNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds genuinely useful non-schema context: data comes from a public route page, results are a capped set of up to 20 recent deals, and billing is $0.002 per successful call via x402 with failures uncharged. What it does not clarify is staleness or provenance of "recent" prices beyond the not-live caveat, which keeps this at a solid but not exceptional level.

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?

The core purpose and the deal/price/insight payload are front-loaded, and the sibling routing follows. However, it is a single densely parenthetical run-on sentence, and the list of returned fields partly duplicates what the output schema already declares, which costs some tightness.

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?

For a read-only lookup with a full input schema and an output schema, the description covers everything an agent needs to decide and act: what the data is, its non-live nature, the sibling alternatives, and the paid-call cost model. Nothing material is left to inference.

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

Parameters3/5

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

Schema coverage is 100%, with both code parameters and the insights flag documented in the schema itself, so the baseline applies. The description mentions route insight question/answer content, which loosely corresponds to the insights flag, but never states its default or that it is a boolean toggle. It adds narrative value rather than new parameter semantics.

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?

The description opens with a specific verb and resource (KAYAK flight route overview between two city/airport codes) and immediately bounds the content: up to 20 recent round-trip deals, the lowest recent price, and published route insights. It explicitly negates the wrong interpretation ("not a live date search"), which lets an agent separate this from a date-specific flight search without opening the schema.

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?

It names two concrete alternatives and the exact condition that selects each: travel_momondo for momondo route prices, travel_rome2rio for Rome2Rio travel ways. It also states this tool is for a route overview rather than a live date search, covering the main wrong-usage case.

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