Skip to main content
Glama

search_flights

Search flights between two airports on a date and get priced offers with airline, times, stops and fare basis, paying per call in USDC over x402.

Instructions

Search flights between two airports on a date. Returns priced offers with airline, times, stops and fare basis. Costs $0.005 per call, paid in USDC over x402 to x402-flight-search. Returns the merchant's artifact and the payment receipt.

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": {
      "origin": "<origin>",
      "destination": "<destination>",
      "departureDate": "<departureDate>"
    },
    "name": "search_flights"
  }
}

Input Schema

NameRequiredDescriptionDefault
railNoPayment rail for this call. Overrides the configured default (auto). auto = whichever rail this agent holds a key for.
adultsNoPassenger count, default 1
originYesIATA origin airport code, e.g. SFO
maxPriceNoCap on total fare
returnDateNoYYYY-MM-DD for a round trip
destinationYesIATA destination airport code, e.g. JFK
departureDateYesYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses a concrete per-call price ($0.005), the currency and payment protocol (USDC over x402 to x402-flight-search), and what the response contains, including the merchant artifact and payment receipt. It omits error/rejection behavior when payment fails and whether offers are paginated or capped.

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?

Three sentences, front-loaded with the operation, then the return shape, then the cost and payment mechanics. Every sentence carries distinct information; nothing is redundant or padded.

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?

No output schema exists, so the description usefully names the returned fields and the non-obvious extras (artifact and payment receipt). Payment cost and rail context are covered, making this largely sufficient; only error handling and result-set limits are left unaddressed.

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 every parameter including the rail enum, adults, maxPrice and returnDate is already documented in the schema. The description adds no parameter-level meaning beyond restating that search happens between two airports on a date, so the baseline of 3 applies.

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?

States a specific verb and resource with clear scope: 'Search flights between two airports on a date,' plus what the results contain (airline, times, stops, fare basis). It doesn't explicitly differentiate itself from the sibling price_flight, so it falls just short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied by the description of the operation; there is no explicit when-to-use guidance, no stated prerequisites, and no routing to alternatives such as price_flight for a specific offer. The cost line tells the agent what the call will spend but not when the call is the right choice.

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