Skip to main content
Glama

get_booking_options

Read-only

Find where and at what price a flight offer's booking token itinerary can be booked to compare available options before reserving.

Instructions

List where, and at what price, an offer's booking_token itinerary can be booked.

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": {
      "booking_token": "<booking_token>"
    },
    "name": "get_booking_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
booking_tokenYes

Output Schema

NameRequiredDescriptionDefault
booking_optionsYes
google_flights_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, open-world retrieval operation. The description adds that it retrieves booking locations and prices for an itinerary, but it does not mention authentication, rate limits, live versus cached pricing, or pagination behavior.

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 definition is a single front-loaded sentence with no wasted wording. The phrasing "where, and at what price" is slightly awkward but still concise and clear.

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

Completeness3/5

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

For a simple one-parameter read tool with an output schema and annotations, the description is mostly sufficient because it states what is retrieved. However, it omits when to use this tool versus the flight-search siblings and does not explain where the booking_token comes from.

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 for the single parameter is 0%, so the description must compensate. It clarifies that booking_token identifies an offer's itinerary, but it does not explain the token format, where to obtain it, or any validity constraints.

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?

The description uses the specific verb "List" and states that it returns booking locations and prices for an offer's booking_token itinerary. It is clearly not a flight search tool like the siblings, though it does not explicitly name an alternative.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no alternatives mentioned. The only implied usage is that an agent should already have a booking_token for an itinerary.

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