Bing Flights MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_flightsA | Search for flights on Bing Flights. Args: origin: Origin airport code (e.g., "SEA") destination: Destination airport code (e.g., "ICN") departure_date: Departure date in YYYY-MM-DD format return_date: Return date in YYYY-MM-DD format (optional) adults: Number of adult passengers (default: 1) children: Number of child passengers (default: 0) infants: Number of infant passengers (default: 0) cabin_class: 0=Economy, 1=Premium Economy, 2=Business, 3=First (default: 0) max_results: Maximum number of results to return (default: 10) headless: Run browser in headless mode (default: True) Returns: Dictionary containing flight search results with structure: - search_params: Search parameters used - results_count: Number of results returned - flights: List of flight options with pricing, airline, times, etc. - timestamp: When the search was performed |
| get_scraper_statusA | Check scraper health and configuration. Returns: Dictionary with scraper status information including: - status: Current status ("healthy") - version: Scraper version - capabilities: Supported features |
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 2 tools
The two tools have completely distinct purposes: get_scraper_status is for health/configuration monitoring, while search_flights is for flight search operations. There is no overlap or ambiguity between these functions.
Both tools follow a consistent verb_noun naming pattern (get_scraper_status, search_flights) with clear, descriptive names. The naming convention is uniform throughout the tool set.
With only 2 tools, this server feels severely under-scoped for a flight search domain. A typical flight search service would need tools for booking, fare details, filtering, or itinerary management, making this set incomplete for practical use.
The tool surface is highly incomplete for flight search functionality. While search_flights covers basic search, there are no tools for booking, retrieving booking details, managing itineraries, or handling cancellations, leaving significant gaps in the domain coverage.