Skip to main content
Glama

Wizzair route network

wizzair_search_routes

Wizzair's route map: pass a station IATA code to list its direct connections (city, country, is_new), or omit it to list every Wizzair city with its destination count. Cached for 6 hours. Data comes live from Wizzair's private booking API (unofficial — may briefly fail if Wizzair rotates or throttles it). Result shape: { source, fetchedAt, query, mode, count, route_map_url, ... }. With station: mode='single_station', station, station_name, country, connections: [{ iata, city, country, is_new }]. Without: mode='all_cities', cities: [{ iata, city, country, country_code, destinations }]. The list key is connections (or cities), never routes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wizzair_search_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
stationNoStation IATA code to list connections from (e.g. WAW). Omit to list all Wizzair cities.
no_cacheNoForce a fresh Wizzair fetch and bypass this server's result cache. Default false.

Output Schema

NameRequiredDescriptionDefault
modeYes
countYes
queryYes
citiesNo
sourceYes
countryNo
stationNo
fetchedAtYes
connectionsNo
station_nameNo
route_map_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses a 6-hour cache, that data comes from an unofficial private booking API, and that calls may briefly fail on rotation or throttling. Those are exactly the operational traits an agent needs before calling.

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?

Front-loaded with the core behavior and mode split, and the closing note about the `connections`/`cities` key being never `routes` is a genuinely useful gotcha. The enumerated result-shape sentence partly duplicates the output schema, costing some tightness.

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

Completeness5/5

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

Covers both call modes, caching, upstream fragility, and the response key naming trap, which is everything an agent needs to invoke and parse correctly. The output schema exists, so the extra shape detail is surplus rather than a gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by tying the presence/absence of `station` to the response `mode` and shape. It does not explicitly connect the 6-hour cache note to the `no_cache` bypass parameter, leaving that inference to 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 ('list its direct connections' / 'list every Wizzair city with its destination count') and makes the route-network scope distinct from the fare/flight/timetable siblings. An agent can tell immediately this is the network-topology tool, not a schedule or pricing tool.

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 branches usage on the `station` parameter: supply it for one station's connections, omit it for the full city list. It does not name the sibling tools or say when to prefer wizzair_search_flights/timetable instead, so it stops short of full alternative routing.

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