Skip to main content
Glama

KAYAK hotel prices for a city: the city's lowest nightly

travel_hotel_booking_sites_direct_hotel_websites
Read-only

KAYAK hotel prices for a city (KAYAK compares booking sites and hotel websites): the city's lowest nightly price headline and KAYAK's 'best hotels' list (usually ~16) with name, star rating, street address, price shown per night in USD, guest rating out of 10 with review count, phone and KAYAK hotel URL. The city is matched with KAYAK's own place search. Prices are KAYAK's recent prices on its public city page, not a live date search. 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": {
      "city": "<city>"
    },
    "name": "travel_hotel_booking_sites_direct_hotel_websites"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name, e.g. Paris, New York, Rome

Output Schema

NameRequiredDescriptionDefault
cityNo
countNo
hotelsNo
sourceNo
currencyNo
lowPriceNo
checkedAtNo
kayakCityIdNo
headlineFromPriceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint it discloses notable behavior: the city string is resolved via KAYAK's own place search (fuzzy matching), the data is cached page pricing rather than live availability, and billing is $0.002 per successful call via x402 with failed calls uncharged. Missing only an indication of result count variance or how stale the page prices may be.

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?

Purpose is front-loaded, followed by the return payload, the data-freshness caveat, and the cost model — a sensible information order. The field enumeration is long and partly redundant with the output schema, which keeps it just short of maximally tight.

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 one-parameter, read-only lookup with an output schema, the description covers everything an agent needs: what it returns, how the city is resolved, the freshness limitation, and the per-call cost/failure policy. No material gap remains.

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% for the single 'city' parameter, so the schema already defines the type and examples. The description adds meaning beyond it by explaining that the city is matched through KAYAK's own place search, implying non-exact matching and tolerance for casual city names.

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

Purpose4/5

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

Names a specific resource (hotel prices for a city) and enumerates the returned fields — lowest nightly price headline and a 'best hotels' list with name, stars, address, USD price, guest rating and URL — so an agent knows exactly what comes back. It clarifies the source (KAYAK aggregating booking sites and hotel websites) but never names a sibling alternative such as the Google Hotels price tool, so differentiation is only implicit.

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

Usage Guidelines3/5

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

Offers one real usage constraint: 'Prices are KAYAK's recent prices on its public city page, not a live date search,' which tells the agent not to rely on it for date-specific pricing. However, it does not name what to use instead for date searches or multi-night stays, so the guidance is implied rather than explicit.

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