Search flights by route, dates, passengers, and cabin class. By Alice, Israel's travel app.
Scored across 1 tool
With only one tool, there is no possibility of confusing it with others; its purpose is entirely clear and self-contained.
The single tool uses a clear verb_noun pattern ('search_flights'), so there is no inconsistency or mixed convention to evaluate.
A single tool is quite thin for a flights server, though it is well-focused and not trivial. The server would feel more complete with at least a couple of related operations.
The core flight search use case is well covered, including categories and booking links, but the server lacks any additional flight-related operations such as status lookup or booking management.
Search flights between any two cities worldwide, including all routes to and from Tel Aviv (TLV / Ben Gurion). Supports Hebrew results with full right-to-left layout. Returns a curated set of options, each tagged with one or more categories:
best: the engine's recommended balance of price, total duration, and stops.
cheapest: lowest total price.
fastest: shortest total travel time.
The categories overlap — a single flight can be both best and cheapest. Each option includes price, total durations, layovers, its categories, and a direct booking link. Options may include seats_remaining — the number of seats left in this booking class at this price; values of 4 or fewer indicate limited availability.
| Name | Required | Description | Default |
|---|---|---|---|
| adults | No | Number of adult passengers (0–9) | |
| origin | Yes | 3-letter IATA city or airport code (e.g. 'TLV', 'LON', 'MAD') | |
| infants | No | Number of infant passengers (0–9) | |
| seniors | No | Number of senior passengers (0–9) | |
| children | No | Number of child passengers (0–9) | |
| language | No | Language for the interactive results widget. Set 'he' when the conversation is in Hebrew; defaults to English. | en |
| destination | Yes | 3-letter IATA city or airport code (e.g. 'TLV', 'LON', 'MAD') | |
| return_date | No | Return date for round trips (YYYY-MM-DD). Omit for one-way. | |
| flight_class | No | Cabin class: tour (economy), tourPlus (premium economy), business, or first | tour |
| departure_date | Yes | Departure date in YYYY-MM-DD format |
| Name | Required | Description |
|---|---|---|
| query | Yes | The search parameters, with defaults applied |
| total | Yes | Total matches found, which may exceed `flights.length` |
| flights | Yes | Matching options, capped at 30 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, open-world, and non-destructive behavior. The description adds useful behavioral details such as the interactive results widget, RTL Hebrew support, and the meaning of seats_remaining/limited availability, going beyond the annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured with actionable output details and category definitions. It is slightly longer than necessary, repeating some info already in the parameter schema, but each sentence adds meaningful context about results and behavior.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity, the description adequately covers the output format, category semantics, booking links, seat availability, and language behavior. It supplies enough context for an agent to call the tool and interpret results correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with every parameter already described. The description adds slight context for origin/destination (TLV/Ben Gurion) and language behavior, but mostly restates information already present in the schema, so it remains at baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: searching flights between any two worldwide cities, including routes to/from Tel Aviv. It specifies the resource (flights) and the action (search), making it unambiguous even without sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context on what the tool does and what it returns, including result categories and booking links. It does not explicitly state when not to use it or mention alternatives, but with no sibling tools, the guidance is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
search_flights1 field changedOutput schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "flights": {
+ "description": "Matching options, capped at 30",
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "categories": {
+ "description": "Which curated selections this flight appeared in; may be more than one",
+ "items": {
+ "enum": [
+ "best",
+ "cheapest",
+ "fastest"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "currency": {
+ "description": "ISO currency code of `price`",
+ "type": "string"
+ },
+ "deep_link": {
+ "description": "Link to complete this booking on alice.co.il",
+ "type": "string"
+ },
+ "inbound": {
+ "$ref": "#/properties/flights/items/properties/outbound",
+ "description": "Absent on one-way trips"
+ },
+ "outbound": {
+ "additionalProperties": false,
+ "properties": {
+ "arrival_local": {
+ "type": "string"
+ },
+ "departure_local": {
+ "type": "string"
+ },
+ "duration_minutes": {
+ "type": "number"
+ },
+ "flights": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "arrival_local": {
+ "type": "string"
+ },
+ "brand": {
+ "description": "Fare brand, e.g. 'LITE', 'FLEX'",
+ "type": "string"
+ },
+ "cabin": {
+ "description": "Raw cabin code, e.g. 'Y', 'C'/'J', 'F'",
+ "type": "string"
+ },
+ "checked_bag_included": {
+ "type": "boolean"
+ },
+ "departure_local": {
+ "type": "string"
+ },
+ "duration_minutes": {
+ "type": "number"
+ },
+ "flight_number": {
+ "type": "string"
+ },
+ "from": {
+ "type": "string"
+ },
+ "seats_remaining": {
+ "type": "number"
+ },
+ "terminal_from": {
+ "type": "string"
+ },
+ "terminal_to": {
+ "type": "string"
+ },
+ "to": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "from",
+ "to",
+ "departure_local",
+ "arrival_local",
+ "flight_number",
+ "duration_minutes"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "from": {
+ "type": "string"
+ },
+ "layovers": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "airport_code": {
+ "type": "string"
+ },
+ "arrival_local": {
+ "type": "string"
+ },
+ "departure_local": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "airport_code",
+ "arrival_local",
+ "departure_local"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "to": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "from",
+ "to",
+ "departure_local",
+ "arrival_local",
+ "duration_minutes",
+ "flights",
+ "layovers"
+ ],
+ "type": "object"
+ },
+ "price": {
+ "description": "Total trip price for all passengers",
+ "type": "number"
+ },
+ "pricing_details": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "passenger_type": {
+ "enum": [
+ "ADT",
+ "CHD",
+ "INF",
+ "YCD"
+ ],
+ "type": "string"
+ },
+ "total_price": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "passenger_type",
+ "total_price"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "seats_remaining": {
+ "description": "Seats bookable at this price; 4 or fewer means limited availability",
+ "type": "number"
+ }
+ },
+ "required": [
+ "outbound",
+ "pricing_details",
+ "categories"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "query": {
+ "additionalProperties": false,
+ "description": "The search parameters, with defaults applied",
+ "properties": {
+ "adults": {
+ "default": 1,
+ "description": "Number of adult passengers (0–9)",
+ "maximum": 9,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "children": {
+ "default": 0,
+ "description": "Number of child passengers (0–9)",
+ "maximum": 9,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "departure_date": {
+ "description": "Departure date in YYYY-MM-DD format",
+ "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+ "type": "string"
+ },
+ "destination": {
+ "description": "3-letter IATA city or airport code (e.g. 'TLV', 'LON', 'MAD')",
+ "maxLength": 3,
+ "minLength": 3,
+ "type": "string"
+ },
+ "flight_class": {
+ "default": "tour",
+ "description": "Cabin class: tour (economy), tourPlus (premium economy), business, or first",
+ "enum": [
+ "tour",
+ "tourPlus",
+ "business",
+ "first"
+ ],
+ "type": "string"
+ },
+ "infants": {
+ "default": 0,
+ "description": "Number of infant passengers (0–9)",
+ "maximum": 9,
+ "minimum": 0,
+ "type": "integer"
+ },
+ "language": {
+ "default": "en",
+ "description": "Language for the interactive results widget. Set 'he' when the conversation is in Hebrew; defaults to English.",
+ "enum": [
+ "en",
+ "he"
+ ],
+ "type": "string"
+ },
+ "origin": {
+ "description": "3-letter IATA city or airport code (e.g. 'TLV', 'LON', 'MAD')",
+ "maxLength": 3,
+ "minLength": 3,
+ "type": "string"
+ },
+ "return_date": {
+ "description": "Return date for round trips (YYYY-MM-DD). Omit for one-way.",
+ "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+ "type": "string"
+ },
+ "seniors": {
+ "default": 0,
+ "description": "Number of senior passengers (0–9)",
+ "maximum": 9,
+ "minimum": 0,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "origin",
+ "destination",
+ "departure_date"
+ ],
+ "type": "object"
+ },
+ "total": {
+ "description": "Total matches found, which may exceed `flights.length`",
+ "type": "integer"
+ }
+ },
+ "required": [
+ "query",
+ "flights",
+ "total"
+ ],
+ "type": "object"
+}search_flightsClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity – fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge – works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge – works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Free, no-login flight search with real-time pricing from multiple airlines.
Search award flight availability and points pricing across 27 airlines and 23 loyalty programs.
Search and book flights and hotels: hundreds of airlines, plus pay-later hotel rates.
Live flight prices and working booking links for AI agents and travel apps.
