Skip to main content
Glama
forgemeshlabs

Travel Assistant MCP

by forgemeshlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_travel_options

Read-onlyIdempotent

Find flight options for a single origin-destination airport pair, with route metadata and external booking links. Supports one-way and round-trip searches.

Instructions

Primary travel search workflow for one origin-destination airport pair. Use when the user wants flight/trip options for a specific route; use compare_routes for multiple routes, build_booking_link only when route details are already known, and get_airport_info only to validate one airport. Read-only, no authentication, no booking side effects. return_date is optional; omit it for one-way trips. Responses include route metadata and may include commission-eligible external booking links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originYesOrigin airport IATA code (e.g. 'LAX', 'JFK'). Case-insensitive.
currencyNoISO 4217 currency code (default: USD). Used in booking link parameters.
destinationYesDestination airport IATA code (e.g. 'LHR', 'NRT'). Case-insensitive.
return_dateNoReturn date in YYYY-MM-DD format. Omit for one-way trips.
departure_dateNoDeparture date in YYYY-MM-DD format. Optional — omit for open date searches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / currency / description
      Previous value: -"Currency code"New value: +"ISO 4217 currency code (default: USD). Used in booking link parameters."
    • changedInput schema / properties / departure_date / description
      Previous value: -"Departure date YYYY-MM-DD"New value: +"Departure date in YYYY-MM-DD format. Optional — omit for open date searches."
    • changedInput schema / properties / destination / description
      Previous value: -"Destination airport IATA code"New value: +"Destination airport IATA code (e.g. 'LHR', 'NRT'). Case-insensitive."
    • changedInput schema / properties / origin / description
      Previous value: -"Origin airport IATA code"New value: +"Origin airport IATA code (e.g. 'LAX', 'JFK'). Case-insensitive."
    • changedInput schema / properties / return_date / description
      Previous value: -"Return date YYYY-MM-DD"New value: +"Return date in YYYY-MM-DD format. Omit for one-way trips."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds 'no authentication' and mentions response contents including commission-eligible links, providing useful context beyond annotations without contradiction.

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 four sentences, each serving a distinct purpose: purpose statement, usage guidelines, behavioral transparency, and parameter hints. No redundant or extraneous information.

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?

Given no output schema, the description mentions response contents (route metadata, booking links). All parameters are covered by schema and description. For a simple search tool with 5 params, this is sufficiently complete.

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 explicitly clarifying the optionality of return_date (one-way trips) and departure_date (open date searches), and by noting the default currency and its role in booking links.

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 clearly states the tool's purpose as the primary search workflow for one origin-destination airport pair. It explicitly distinguishes this from sibling tools like compare_routes and build_booking_link, making selection unambiguous.

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?

The description provides explicit when-to-use guidance, including using compare_routes for multiple routes and build_booking_link only after route details are known. It also clarifies optional parameters like return_date for one-way trips.

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