Look up flight status, times, gates, and route details form AI assistants. A GoTravelX account and api key are required; available details vary by flight.
Scored across 3 tools
Each tool targets a distinct resource and action: two account introspection tools (balance, profile) and one flight lookup. There is no plausible way to confuse a carrier-flight-number lookup with an account query, and the descriptions reinforce the boundaries.
All three tools use the same get_<resource> snake_case pattern (get_account_balance, get_account_profile, get_flight_status). The convention is predictable and immediately readable.
Three tools is a tight, well-scoped surface for a single-purpose flight status API, with no redundant entries. It sits on the thin side, since two of the three are account-housekeeping rather than domain lookup capability.
The core workflow (identify account, check quota, look up a flight) is fully covered with no dead ends, and unsupported carriers fail without cost. A gap remains: there is no tool to enumerate supported carriers, forcing the agent to discover them by trial-and-error or an external webpage.
Check the connected GoTravelX account’s remaining free and paid result sets. Does not spend a result set.
Inputs: no named parameters. Returns: free, paid
Identify the connected GoTravelX account. Does not spend a result set.
Inputs: no named parameters. Returns: id, name
Look up a flight for a GoTravelX-supported carrier using its carrier-prefixed number and local departure date. Supports the carriers listed on flightdata.online/mcp; Delta (DL) is not supported. A valid supported-carrier lookup spends one result set, even if the flight is not found. Unsupported carriers are rejected without a charge.
Inputs: date (required), flight (required). Returns: found, flight, resultSetsRemaining
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.
