Skip to main content
Glama

Airsockfly

Search flights

search_flights
Read-onlyIdempotent

Search flights between two airports or cities. Returns offers with the price in grosze, schedule, fare family and a link to the offer page. Use suggest_places first when you only know a city name.

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": {
      "fromCode": "<fromCode>",
      "toCode": "<toCode>",
      "departureDate": "<departureDate>"
    },
    "name": "search_flights"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of offers to return, from 1 to 30. Default 10.
adultsNoNumber of adults.
toCityNoArrival city name. Defaults to the IATA code.
toCodeYesIATA code of the arrival airport or city, for example BCN.
infantsNoNumber of infants under 2 travelling on an adult's lap.
childrenNoNumber of children aged 2 to 17.
fromCityNoDeparture city name. Defaults to the IATA code.
fromCodeYesIATA code of the departure airport or city, for example WAW.
cabinClassNoCabin class.
returnDateNoReturn date, YYYY-MM-DD. Omit for a one-way flight.
childrenAgesNoAge of each child in years, in the same order as children.
departureDateYesOutbound date, YYYY-MM-DD.
includeNearbyNoAlso search nearby alternative airports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior: the returned price is in grosze (a non-obvious currency unit), plus schedule, fare family and an offer link. It stops short of disclosing pagination, result-count limits or how passenger counts affect pricing, which are the remaining real unknowns.

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

Conciseness5/5

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

Three short sentences, front-loaded with the core action and payload, with the routing caveat last. No filler and nothing repeated from the schema.

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

Completeness4/5

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

For a 13-parameter search tool with no output schema, the description does the important work of summarizing return fields and the currency unit for prices. What is missing, such as pagination behavior and whether prices are per passenger, is secondary but would complete the picture.

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

Parameters3/5

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

Schema description coverage is 100%, so every one of the 13 parameters is already documented in the schema, and the description adds no format or constraint detail beyond it. Baseline 3 is appropriate; the only semantic hint, that city names default to IATA codes, is already in the schema.

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?

States a specific verb and resource (search flights) plus the scope (between two airports or cities), and enumerates the return payload so the agent knows what a successful call yields. This distinguishes it from siblings like search_hotels or suggest_places without ambiguity.

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

Usage Guidelines4/5

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

Explicitly routes the agent to suggest_places when only a city name is known, which is the main selection pitfall for this tool. There is no when-not guidance for other siblings, but for a clearly scoped search endpoint the single routing rule covers the realistic confusion.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources