Skip to main content
Glama

Skyscanner flight prices from its public route page: lowest

travel_skyscanner
Read-only

Skyscanner flight prices from its public route page (Skyscanner codes, e.g. lond to pari, ist to lond): lowest recent fare, up to 16 cheapest recent one-way deals (date, airline, airports, direct or not, USD price, when seen), cheapest fare per month for a year, route facts and Skyscanner's FAQ answers. Not a live date search. Related tools on this server, for a different need: travel_momondo when you need momondo flight prices from its public route page for two; travel_kayak when you need KAYAK flight route overview between two city or airport. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "travel_skyscanner"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesSkyscanner destination code, e.g. pari, mia, lond
fromYesSkyscanner origin code: 3-letter airport (ist, jfk) or 4-letter city code (lond, nyca, pari)

Output Schema

NameRequiredDescriptionDefault
toNo
faqNo
fromNo
countNo
dealsNo
factsNo
routeNo
sourceNo
currencyNo
lowPriceNo
checkedAtNo
cheapestByMonthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety and open-world behavior are covered. The description adds genuinely useful non-schema context: the exact cost ($0.002 per successful call, charged via x402 in USDC on Base/Solana and 10 more networks) and that failed calls are not charged. It does not mention rate limits, latency, or freshness of 'recent' fares, and the output schema already covers return shape, so with annotations doing part of the work this lands at adequate rather than rich.

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?

One long but front-loaded sentence: the primary capability and its returned data come first, then the negative scope, then the sibling routing, then pricing. No filler, though the single-sentence packing makes it dense and slightly harder to scan than a short bulleted structure would be.

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 2-parameter read-only tool with a full output schema, the description covers what it returns, what it does not do, how to choose alternatives, and the billing model. The only meaningful gap is any indication of data staleness for 'recent' fares or of response size/pagination for the up-to-16 deals.

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% and the schema already documents both parameters, including that 'from' accepts a 3-letter airport or 4-letter city code. The description's 'Skyscanner codes, e.g. lond to pari, ist to lond' largely restates the schema examples, adding only the minor nuance that both endpoints are Skyscanner-specific codes. Baseline 3 is appropriate since the schema carries the detail.

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 ('Skyscanner flight prices from its public route page') and enumerates the concrete outputs: lowest recent fare, up to 16 cheapest recent one-way deals, cheapest fare per month for a year, route facts and FAQ answers. It explicitly rules out one interpretation ('Not a live date search') and names the sibling tools that serve different needs, so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit routing guidance: 'travel_momondo when you need momondo flight prices ... for two' and 'travel_kayak when you need KAYAK flight route overview', each with the condition that selects it. It also states the negative case ('Not a live date search'), which tells the agent when not to use it.

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