Skip to main content
Glama

Booking.com hotel price guide for a city: the lowest 'from'

travel_booking_com
Read-only

Booking.com hotel price guide for a city (e.g. fr / paris): the lowest 'from' nightly price in the page title and Booking.com's published average nightly prices for 3-, 4- and 5-star hotels (typical, this weekend, tonight, as stated on the city page), plus the hotels Booking.com names as best or popular with their URLs. Currency selectable. Averages are Booking.com's own figures, not a live date search. Related tools on this server, for a different need: travel_booking_com_reviews when you need Booking.com guest reviews featured on a city page: hotel; travel_booking_com_hotels when you need hotels featured on a Booking.com city page: name, property. 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": {
      "country": "<country>",
      "city": "<city>"
    },
    "name": "travel_booking_com"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity as in Booking.com city URLs, e.g. paris, new-york, rome
countryYesTwo-letter country code as in Booking.com city URLs, e.g. us, fr, gb
currencyNoThree-letter currency code (default USD)

Output Schema

NameRequiredDescriptionDefault
cityNo
destIdNo
sourceNo
countryNo
currencyNo
checkedAtNo
fromPriceNo
namedHotelsNo
fromPriceTextNo
averageNightlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds materially: the averages are Booking.com's own published figures rather than live date-scoped results, and it discloses the cost model ($0.002 per successful call via x402, failures not charged). Both are behavioral 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 core output description and zero filler sentences; every clause carries information. It is, however, a single dense run-on sentence with parenthetical stacking that would read faster if split into output, caveat, alternatives, and pricing blocks.

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 an output schema exists, the description need not describe return shape, and it covers what remains: data provenance/staleness, currency selection, and cost. Nothing an agent needs to decide or invoke correctly appears to be missing.

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 description coverage is 100%, so all three parameters are already documented with formats and examples. The description adds only the 'e.g. fr / paris' pairing and 'Currency selectable', which is marginal reinforcement rather than new semantics, so the baseline 3 applies.

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 resource (Booking.com city price guide) and enumerates exactly what is returned: the lowest 'from' nightly price, Booking.com's published averages for 3-, 4- and 5-star hotels across named time windows, and named best/popular hotels with URLs. It explicitly distinguishes itself from sibling tools travel_booking_com_reviews and travel_booking_com_hotels.

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?

Names the two nearest alternatives and the exact need that selects each ('when you need guest reviews', 'when you need hotels ... name, property'). It also sets a firm boundary by declaring the data is 'not a live date search', which tells the agent when this tool is the wrong choice.

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