Skip to main content
Glama

fa_search_flights_advanced

Read-only

Search flights using structured queries with operator-key-value predicates for complex filtering on ident, origin, destination, altitude, and more.

Instructions

Search flights using AeroAPI's full structured query language (more expressive than fa_search_flights). The query is a space-separated list of {operator key value} predicates, e.g. "{match ident UAL*} {> alt 300} {= dest KLAX}". Operators: true/false/null/notnull/=/!=/</>/<=/>=, match/notmatch (case-insensitive wildcards), range (two values), in/orig_or_dest/aircraftType/ident/ident_or_reg ({a b c} value lists), airline (1=airline, 0=GA). Common keys: ident, orig, dest (ICAO codes), aircraftType, alt (hundreds of ft), prefix, lifeguard, cancelled, arrived.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesStructured "{operator key value}" query, e.g. {match ident UAL*} {> alt 300}
cursorNoOpaque paging cursor from a previous response's links.next
max_pagesNoMax pages to fetch (AeroAPI default: 1)
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint. The description adds substantial behavioral context on the query language syntax, operators, and keys, beyond what annotations provide. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively dense but front-loaded with purpose and example. It could be slightly more concise, but each sentence adds value.

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?

For a complex tool with a structured query language, the description covers input semantics well. However, it lacks any mention of output structure, which is partially mitigated by the tool being a search.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description greatly enriches the query parameter with detailed syntax, operators, and examples, far exceeding the schema's minimal description.

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 searches flights using a structured query language, explicitly contrasting with 'fa_search_flights' by saying 'more expressive'. It provides a concrete example, making the purpose and resource clear.

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?

The description implies use for advanced queries by contrasting with 'fa_search_flights', but does not explicitly state when to use or when not to use this tool, nor does it list alternatives.

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/chrischall/flightaware-mcp'

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