Skip to main content
Glama

Find cheap flights for a break

find_trips
Read-onlyIdempotent

Find the cheapest return flights from a departure airport that fit a break, one per destination, cheapest first, with booking links. Prices are cached airline fares in the departure country's currency (GBP, EUR, AUD or USD) and can change; if the result says sample, they are example prices only. Links go through leavehacker.app/go and are affiliate links: Leave Hacker may earn a commission if you book, at no extra cost to you. Say so when you share them. Use for "Find cheap flights from Manchester that fit the May bank holiday weekend" (work out the break's dates with best_days_to_book first).

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>",
      "depart": "<depart>",
      "return": "<return>"
    },
    "name": "find_trips"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many destinations to return, up to 20. Default 10.
departYesOutbound date, the first day of the break (yyyy-MM-dd).
originYesDeparture airport or city IATA code, e.g. MAN (Manchester), LGW (Gatwick), EDI (Edinburgh), BHX, LON (all London airports).
returnYesReturn date, the last day of the break (yyyy-MM-dd).

Output Schema

NameRequiredDescriptionDefault
faresYes
departYes
originYes
returnYes
sampleYesTrue: example prices, not real offers
currencyYesISO 4217: GBP from the UK, EUR from Ireland, AUD from Australia, USD from the US
affiliateYes
priceNoteYes
disclosureYes
searchAllUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / currency / const
      Removed value: -"GBP"
    • addedOutput schema / properties / currency / description
      Added value: +"ISO 4217: GBP from the UK, EUR from Ireland, AUD from Australia, USD from the US"
    • changedOutput schema / properties / fares / items / properties / price / description
      Previous value: -"GBP per person, return"New value: +"Per person, return, in currency"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already signal a safe read (readOnly, idempotent, openWorld, non-destructive), and the description adds substantial context beyond them: fares are cached and can change, currency depends on departure country, results may be flagged 'sample' as example prices, and links are affiliate redirects requiring disclosure to the user. This is meaningful operational and compliance detail an agent could not infer.

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?

Front-loads the core operation and result shape before details, and the affiliate disclosure is genuinely necessary content. It is dense but not padded; the only slight drag is the currency-parenthetical mid-sentence.

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?

Output schema exists, so return values need not be explained, and for a 4-param read tool the description covers everything an agent needs: date sourcing via the sibling tool, price provenance, currency, sample-price caveat, and the affiliate-link disclosure obligation.

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 origin/depart/return/limit are already documented, making 3 the baseline. The description adds ordering semantics ('cheapest first', 'one per destination') that clarify what limit actually counts, which the schema does not state — a modest but real value-add.

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?

States a specific verb and resource — find the cheapest return flights from a departure airport — plus result shape (one per destination, cheapest first, with booking links). This distinguishes it cleanly from siblings like best_days_to_book and plan_leave_year, which handle dates and planning rather than fare lookup.

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?

Gives a concrete use case ("Find cheap flights from Manchester that fit the May bank holiday weekend") and an explicit prerequisite: work out the break's dates with best_days_to_book first. An agent knows both when to call it and what to chain beforehand.

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.

Resources