Skip to main content
Glama
CPLX

Flighty MCP Server

by CPLX

List Friend Flights

flighty_list_friend_flights
Read-onlyIdempotent

Retrieve flights from friends connected in Flighty. Filter by friend name, upcoming flights, or specific year to see their travel schedules.

Instructions

List flights belonging to the user's connected friends in Flighty. Excludes the user's own flights (use flighty_list_flights for those).

Same filtering as flighty_list_flights:

  • No filter: all friend flights, sorted descending (most recent first)

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

  • year=2025: flights from that year, sorted descending

All timestamps are UTC. Returns the same flight schema as flighty_list_flights, plus a friend_name field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
friend_nameNoFilter by friend's name (partial, case-insensitive match on full name or first name)
upcoming_onlyNoOnly future flights (sorted soonest first)
yearNoFilter to a specific year (e.g. 2025)
limitNoMaximum results
offsetNoPagination offset
Behavior4/5

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

Annotations already indicate readOnly, non-destructive, idempotent. Description adds useful context: timestamps in UTC, return schema includes friend_name, sorting based on filter. No contradictions.

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?

Concise and well-structured with bullet points for filtering options. Every sentence adds value; no unnecessary text.

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, but description explains return format (same as flighty_list_flights plus friend_name). Adequate for a list tool with many siblings; covers key behavioral aspects.

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%, but description adds value by explaining friend_name matching (partial, case-insensitive) and the sorting implication of upcoming_only and year.

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 it lists flights belonging to connected friends, explicitly excludes user's own flights, and distinguishes from the sibling tool flighty_list_flights.

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?

Provides explicit guidance on when to use this tool versus flighty_list_flights, and describes filtering behaviors for no filter, upcoming_only, and year parameters.

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