amadeus-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_MODE | No | Operating mode: 'mock' (default, no credentials) or 'live' (requires Amadeus API keys). | mock |
| AMADEUS_CLIENT_ID | No | Your Amadeus API client ID. | |
| AMADEUS_CLIENT_SECRET | No | Your Amadeus API client secret. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| flight_statusA | Get the status of a flight (scheduled vs estimated times, delay, cancellation). Args: carrier_code: IATA carrier code, e.g. "AF". flight_number: Flight number without carrier, e.g. "1234". departure_date: Scheduled departure date, ISO format "YYYY-MM-DD". |
| predict_delayA | Predict the probability that a flight is delayed by more than 2 hours. Args: origin: Origin IATA airport code, e.g. "NCE". destination: Destination IATA airport code, e.g. "CDG". departure_datetime: Scheduled departure, ISO format "YYYY-MM-DDTHH:MM". carrier_code: IATA carrier code, e.g. "AF". flight_number: Flight number, e.g. "1234". |
| search_flightsA | Search bookable flights for a route and date (non-stop, one adult). Args: origin: Origin IATA airport code, e.g. "NCE". destination: Destination IATA airport code, e.g. "CDG". departure_date: ISO format "YYYY-MM-DD". max_results: Maximum number of offers to return (default 5). |
| passenger_rightsA | Look up passenger rights and carrier disruption policies (EU261, rebooking, baggage, duty of care). Returns the most relevant policy passages with sources, so every entitlement you state can be cited. Args: question: Natural-language question, e.g. "compensation for a 3 hour delay". top_k: Number of passages to return (default 3). |
| handle_disruptionA | Run the full disruption-handling agent for a flight: status check, disruption assessment, rebooking search, policy retrieval and a grounded passenger message. Args: carrier_code: IATA carrier code, e.g. "AF". flight_number: Flight number, e.g. "1234". departure_date: ISO format "YYYY-MM-DD". scenario: In mock mode only: "delay", "cancellation" or "on_time". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: one checks flight status, one runs a disruption agent, one retrieves passenger rights, one predicts delays, and one searches flights. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., flight_status, handle_disruption, search_flights).
5 tools is a reasonable count for a flight disruption management server. It covers core functions without being too sparse or excessive, though a few more specialized tools could exist.
The tool surface covers the main workflows: status, disruption handling, rights lookup, prediction, and search. Some minor gaps like airport code resolution or direct rebooking are absent but the handle_disruption tool may encapsulate those.