Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

booking_flights_autocomplete

Get Booking.com airport and city autocomplete suggestions for flight searches from a city, airport, or code; optionally bias by origin.

Instructions

Booking.com flight autocomplete. Returns Booking.com flight-search location suggestions (airports and cities) for query, which is required. type is to (default) or from; origin and origin_type bias results by proximity. Each result has name, code, type, country, country_name and region_name. Combine code and type as {code}.{TYPE} for booking-flights-search.

Input Schema

NameRequiredDescriptionDefault
typeNoLocation role, default to
queryYesCity or airport name/code to search
originNoOptional origin location code, biases results by proximity
origin_typeNoOrigin location type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "to",
+  "from"
+]
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: it states that results are Booking.com flight-search location suggestions, lists returned fields, and explains how `origin` biases results by proximity. It does not cover error behavior or result limits, but covers the core behavior clearly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and compact, moving from purpose to parameters to return format to downstream usage. Every sentence adds operational value without repetition.

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 four parameters, full schema coverage, and no output schema, the description supplies the missing return-shape details and downstream formatting needed to call the tool correctly. Nothing essential for an autocomplete tool is omitted.

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%, so the baseline is 3. The description adds value by stating that `query` is required, that `type` defaults to `to`, and that `origin` and `origin_type` bias results by proximity, plus how to format results for the downstream search tool.

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 states a specific verb and resource: it returns Booking.com flight-search location suggestions for airports and cities. It also distinguishes this autocomplete tool from the downstream booking_flights_search tool by explaining how to combine `code` and `type`.

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?

The description makes clear that `query` is required and explains the role of `type`, `origin`, and `origin_type`. It also connects the output to booking-flights-search, giving clear usage context, though it does not explicitly state when not to use the tool.

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

Deploy Server

Other Tools