Skip to main content
Glama
CPLX

Flighty MCP Server

by CPLX

List My Flights

flighty_list_flights
Read-onlyIdempotent

List your flights from Flighty, with options to filter by upcoming departures, specific year, and paginate results.

Instructions

List the user's flights from Flighty. Does NOT include friends' flights (use flighty_list_friend_flights for that).

Filtering:

  • No filter: returns ALL flights (upcoming + past), sorted by departure date descending (most recent first)

  • upcoming_only=true: only flights with future departures, sorted soonest first — the first result is the user's next flight

  • year=2025: only flights from that year, sorted descending (matches the app's past-by-year view)

NOTE: upcoming_only only returns flights that have not yet departed. For the user's current travel context (in-progress flights, recently landed, about to depart), use flighty_current_flights instead.

All timestamps are UTC.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
upcoming_onlyNoOnly return flights departing in the future (sorted soonest first)
yearNoFilter to a specific year (e.g. 2025). Shows past flights from that year, matching the Flighty app's year view.
limitNoMaximum number of flights to return
offsetNoNumber of flights to skip for pagination
Behavior5/5

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

Description adds behavioral details beyond annotations: default sorting (descending by departure date), effect of upcoming_only on sort order (soonest first), year filter matching app view, and that all timestamps are UTC. Annotations already confirm read-only, non-destructive, idempotent; description adds value 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?

Description is concise (4 sentences plus bullet-like lines). Purpose is front-loaded, followed by exclusions and filtering details. Every sentence serves a purpose. No fluff.

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 4 optional parameters, no required ones, read-only hints, and no output schema, the description covers all needed behavioral aspects: default behavior, sorting, timezone, handling of upcoming_only vs current flights, and ties to sibling tools. It's complete for an AI agent to select and invoke correctly.

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 covers all 4 parameters (100% coverage). Description adds extra context: for upcoming_only, clarifies it only returns not-yet-departed flights; for year, adds sorting descending. These go beyond the schema's descriptions, but limit and offset are not elaborated further. Overall useful but not extensive.

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?

Description clearly states it lists user's flights from Flighty, specifies it excludes friends' flights, and points to the sibling tool flighty_list_friend_flights for that purpose. It also distinguishes from flighty_current_flights via a note. The verb 'list' and resource 'user's flights' are precise.

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?

Explicitly tells when to use this tool (list user's flights) and when not to (for friends' flights or current travel context), providing exact sibling tools (flighty_list_friend_flights, flighty_current_flights). Also explains filtering scenarios like upcoming_only and year filter with expected sorting behavior.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CPLX/flighty-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server