Skip to main content
Glama

Pro Flight Search Airport Delays

by com.proflightsearch

Search supported airports

search_supported_airports
Read-onlyIdempotent

Search Pro Flight Search tracked airports when a user's airport reference is ambiguous. Returns matching IATA codes to use with get_airport_delay_status. Call this before airport status when the user says a city name like London or Chicago.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesAirport code, city, or airport name to search. Examples: London, Paris, Chicago, ORD.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query used to find tracked airports.
matchesYesTracked airport matches that can be used with get_airport_delay_status or airport.get_delay_status.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate read-only and idempotent. Description adds that it returns matching IATA codes and the intended flow, consistent with annotations.

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?

Two sentences with no wasted words. Front-loaded with verb and resource, then usage guidance. Highly efficient.

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?

Complete for a search tool with output schema. Explains trigger and downstream tool. Could mention ordering or limits but not necessary given output schema.

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 covers 100% of the parameter with examples. Description adds context but does not significantly enhance beyond schema, so baseline 3 is appropriate.

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 explicitly states the tool searches tracked airports when ambiguous and returns IATA codes for get_airport_delay_status. It distinguishes from siblings by specifying when to call it.

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

Usage Guidelines4/5

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

Clear usage context: call when user's airport reference is ambiguous, before airport status for city names. Does not explicitly state when not to use but provides solid guidance.

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

All Pro Flight Search Airport Delays toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

The two distinct functionalities (search airport and get delay status) are clearly separated, and the aliases are explicitly documented as such, so an agent can easily disambiguate.

Naming Consistency2/5

The naming is inconsistent: two tools use dot-notation (airport.get_delay_status, airport.search_supported) while two use underscore (get_airport_delay_status, search_supported_airports), mixing conventions.

Tool Count3/5

With only 2 unique tools (despite 4 listed), the server is narrowly scoped. This is borderline acceptable for a specific domain like airport delays, but feels thin.

Completeness5/5

The server fully covers its stated purpose: search for airports to resolve ambiguous references and get live delay status. No obvious gaps for airport-level delay queries.

Resources