Skip to main content
Glama
Sign In
All Flights MCP

All Flights MCP

by shayben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

search_flights

Read-only

Search multiple flight providers concurrently and get a normalized, deduplicated list of itineraries.

Instructions

Search all configured flight providers concurrently, normalize their offers, and deduplicate equivalent itineraries.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "origin": "<origin>",
      "destination": "<destination>",
      "departureDate": "<departureDate>"
    },
    "name": "search_flights"
  }
}

Input Schema

NameRequiredDescriptionDefault
cabinNoeconomy
adultsNo
originYesOrigin IATA airport or city code
currencyNoISO 4217 currency
maxStopsNo
providersNoProvider IDs to query
timeoutMsNo
maxResultsNo
returnDateNoOptional return date, YYYY-MM-DD
destinationYesDestination IATA airport or city code
departureDateYesDeparture date, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

The description adds value beyond annotations by disclosing concurrent querying of providers, normalization, and deduplication. Annotations already indicate read-only and open-world behavior, and the description complements this without contradiction. However, it still omits details like error handling or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that effectively summarizes the core function. It is concise and front-loaded with the key action. However, it could be broken into multiple sentences for improved readability, but overall it is appropriately sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (11 parameters, no output schema), the description is insufficient. It does not explain the output format, how to interpret results, or what edge cases exist. The annotations and schema alone do not provide complete guidance for a production tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at 55%, many parameters lack description. The tool description does not elaborate on parameter meanings beyond what is already in the schema. It does not compensate for the missing schema descriptions, leaving ambiguity for parameters like 'providers' or 'timeoutMs'.

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?

The description clearly specifies the verb 'Search', the resource 'flights', and the unique behavior: searching all configured providers concurrently, normalizing offers, and deduplicating. It distinguishes itself from sibling tools like 'list_providers' and 'search_date_range' which have different scopes.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs. alternatives is provided. The description only states what the tool does, but does not mention when to prefer it over 'search_date_range' or other tools. The context of usage is implied but not articulated.

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

Deploy Server

Other Tools