Skip to main content
Glama

FlyBest Travel — Hotel Booking with Advisor Benefits

Search hotels

sabre_hotel_search
Read-onlyIdempotent

Hotels near a place: names, Sabre hotel codes, star rating, distance and a provisional lowest rate per property; preferred-partner properties are flagged. It answers questions about hotels, where to stay, hotel prices and availability with live, bookable rates and the partner benefits attached to them. check_in and check_out are optional: without them it searches sample dates (about 30 days ahead, 2 nights, 2 adults unless adults is given), and the result's first line names those dates and says prices depend on the traveller's own dates. The prices are provisional — the bookable rates, terms and benefits of a property come from sabre_hotel_rates_coded. Results then give a note for the traveller about booking in this conversation and end with a short reminder. The traveller can confirm their chosen option in this chat to receive its secure payment page. A membership question appears near the start when the hotels have a known loyalty programme, no number was supplied and the search used the traveller's own dates. A hotel that has a page in the flybest.org hotel directory carries a "hotel details on flybest.org" link, which the answer shows next to that hotel.

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": {
      "location": "<location>"
    },
    "name": "sabre_hotel_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
adultsNo
check_inNoYYYY-MM-DD. Optional: without check_in and check_out the search uses sample dates and its first line names them.
latitudeNoOptional, together with longitude: the centre of the place in decimal degrees, for a place a search by name could not locate. Accepted only where the location text confirms it — within 50 km of a city it names, or inside the country it names; otherwise the call is refused and nothing is searched.
locationYes3-letter city/airport code (SBA), a city name — "Paris", "东京" — or a neighbourhood, resort or hotel with its city and country: "Namba, Osaka, Japan", "Soma Bay, Egypt". The city written after a comma is checked against, and searched when the first part is not a place on its own.
check_outNoYYYY-MM-DD. Optional; with check_in alone the sample stay is 2 nights.
longitudeNoOptional, together with latitude (decimal degrees).
radius_milesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / all_programmes
      Removed value: -{
      -  "description": "default true; one query per loaded consortia programme so PP properties are flagged",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / rate_codes
      Removed value: -{
      -  "description": "narrow to specific codes, e.g. [\"API\"], [\"WMP\"] Hilton for Luxury, [\"BC9\"] Bellini Club",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
  2. Changed3 schema fields changed
    • changedInput schema / properties / check_in / description
      Previous value: -"YYYY-MM-DD"New value: +"YYYY-MM-DD. Optional: without check_in and check_out the search uses sample dates and its first line names them."
    • changedInput schema / properties / check_out / description
      Previous value: -"YYYY-MM-DD"New value: +"YYYY-MM-DD. Optional; with check_in alone the sample stay is 2 nights."
    • changedInput schema / required
      Previous value: -[
      -  "location",
      -  "check_in",
      -  "check_out"
      -]New value: +[
      +  "location"
      +]
  3. Changed3 schema fields changed
    • addedInput schema / properties / latitude
      Added value: +{
      +  "description": "Optional, together with longitude: the centre of the place in decimal degrees, for a place a search by name could not locate. Accepted only where the location text confirms it — within 50 km of a city it names, or inside the country it names; otherwise the call is refused and nothing is searched.",
      +  "type": "number"
      +}
    • changedInput schema / properties / location / description
      Previous value: -"3-letter city/airport code (SBA), or a city name — \"Paris\", \"东京\", or \"City, CC\" for anywhere unusual"New value: +"3-letter city/airport code (SBA), a city name — \"Paris\", \"东京\" — or a neighbourhood, resort or hotel with its city and country: \"Namba, Osaka, Japan\", \"Soma Bay, Egypt\". The city written after a comma is checked against, and searched when the first part is not a place on its own."
    • addedInput schema / properties / longitude
      Added value: +{
      +  "description": "Optional, together with latitude (decimal degrees).",
      +  "type": "number"
      +}
  4. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world behavior, yet the description still adds substantial context: prices are provisional, undated searches use sample dates disclosed on the first result line, a membership question may appear, and confirmation in chat yields a secure payment page. These are behavioral traits no annotation or schema field conveys.

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?

The lead sentence is well front-loaded, but the block then drifts into traveller-facing flow detail (result notes, membership prompt placement, flybest.org link rendering) that is long and only loosely tied to invoking the tool correctly. It is a single dense paragraph with no structural breaks for the fallback rules or the sibling hand-off.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does so well by enumerating the fields and the provisional-rate caveat. Gaps remain around radius_miles semantics and result pagination/volume, but the core callable behavior is covered.

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?

At 71% schema coverage the schema does much of the work, and the description mostly restates it (optional dates, sample stay of 2 nights, 2 adults default). radius_miles has neither a schema description nor any mention in the description, leaving one parameter undocumented in both places.

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 and resource plus the exact return fields (names, Sabre hotel codes, star rating, distance, provisional lowest rate, preferred-partner flags). It explicitly separates itself from sabre_hotel_rates_coded, so an agent can distinguish the two without opening either 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?

Names the alternative explicitly (bookable rates come from sabre_hotel_rates_coded) and explains the optional-date fallback and the latitude/longitude acceptance rules. It stops short of stating when not to use it or naming the other siblings (content, card link, currency), so it is clear but not exhaustive.

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.