Akkilahdot travel search

Server Details

Realtime package holiday and charter flight prices from Finland. Inventory not on Google Flights.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 99.9% over 75 days
Last Tested: 2026-11-02 19:27
Transport: Streamable HTTP · MCP 2025-06-18
URL

TDQS

A3.9/5.0

Scored 2026-11-02 19:35 across 2 tools

Disambiguation5/5

The two tools target clearly distinct products: flight-only search versus flight-plus-hotel package search. Descriptions explicitly cross-reference each other, telling the agent which tool to use for each query type.

Naming Consistency5/5

Both names follow the same search_<resource> snake_case pattern (search_flights, search_holidays). Naming is predictable and consistent.

Tool Count4/5

Two tools are appropriate for a narrow travel-search server covering its two main product types, but the surface is somewhat thin and offers no additional operations beyond search.

Completeness4/5

The server covers the two primary search flows (flight-only and package holidays) and returns availability, pricing, hotel info, and booking links. Minor gaps exist, such as hotel-only or activity searches, but core search workflows are covered.

Available Tools

2 tools

search_flightsEtsi lentotarjouksia SuomestaA

Read-only

Inspect

Hae reaaliaikaisia tilauslentotarjouksia (vain lento) sivustolta akkilahdot.fi. Käytä, kun kysytään lentoja ilman majoitusta, esim. 'pelkkä lento', 'lentopaikka', 'tilauslento ilman hotellia' ja 'lentoliput'. Palauttaa saatavilla olevat pelkät lennot, ei pakettimatkoja. Lento + hotelli -hakuihin käytä search_holidays-työkalua.

Name	Required	Description	Default
`adt`	No	Aikuisten määrä (NDC: PaxType=ADT), oletus 1
`chd`	No	Lasten määrä (NDC: PaxType=CHD), oletus 0
`inf`	No	Vauvojen määrä (NDC: PaxType=INF), oletus 0
`dest`	No	IATA-koodi kohdekentälle, esim. AYT, AGP, TFS
`orig`	No	IATA-koodi lähtökentälle, esim. HEL, OUL, TLL
`sort`	No	Järjestys, oletus price_asc	price_asc
`limit`	No	Tarjousten määrä (1-25), oletus 10
`direct`	No	Vain suorat lennot (NDC: StopQuantity=0)
`dep_date`	No	Tarkka lähtöpäivä (YYYY-MM-DD)
`ret_date`	No	Tarkka paluupäivä (YYYY-MM-DD)
`max_price`	No	Maksimihinta (NDC: PriceRangeFilter.MaxAmount)
`nights_max`	No	Enimmäismäärä öitä (vendor extension, ei NDC)
`nights_min`	No	Vähimmäismäärä öitä (vendor extension, ei NDC)
`dep_date_to`	No	Viimeisin lähtöpäivä (YYYY-MM-DD)
`ret_date_to`	No	Viimeisin paluupäivä (YYYY-MM-DD)
`dep_date_from`	No	Aikaisin lähtöpäivä (YYYY-MM-DD)
`ret_date_from`	No	Aikaisin paluupäivä (YYYY-MM-DD)

Output Schema

Name	Required	Description
`total`	No
`offers`	No

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: offers are real-time, come from akkilahdot.fi, and return only flight-only inventory rather than packages. It does not discuss rate limits or pagination, but an output schema exists to cover return structure.

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?

The description is four focused sentences: purpose first, then usage examples, then return scope, then sibling routing. Every sentence earns its place and the most important selection guidance is front-loaded.

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?

Given 17 optional parameters, full schema description coverage, existing annotations, and an output schema, the description supplies the essential purpose, scope, and sibling routing. It does not mention operational details such as whether origin defaults to Finland or any rate limits, but those are not necessary for correct selection and invocation.

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 all 17 parameters are already documented in the input schema, including IATA codes, date formats, passenger counts, and the sort enum. The description does not add parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific verb and resource: it fetches real-time charter flight offers, explicitly flight-only. It clearly distinguishes itself from search_holidays by stating that package trips are not returned and that flight+hotel searches belong to the sibling tool.

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?

It states exactly when to use the tool with concrete user phrasings such as 'pelkkä lento' and 'lentoliput', and names the alternative tool search_holidays for the excluded flight+hotel case. No inference about when to choose this tool versus its sibling is left to the agent.

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

search_holidaysEtsi äkkilähtöjä ja pakettimatkoja SuomestaB

Read-only

Inspect

Hae saatavilla olevia pakettimatkoja, jotka sisältävät lennot ja majoituksen ja lähtevät Suomesta. Palauttaa käyttäjän hakuehtoja vastaavat ajantasaiset hinnat, saatavuuden, hotellitiedot ja varauslinkit. Etsi saatavilla olevia pakettimatkoja Suomesta hakukriteerien perusteella.

Name	Required	Description
`lat`	No	Leveysasteikko desimaaliluvuissa, käytetään lon ja säteen kanssa
`lon`	No	Pituusasteikko desimaaliluvuissa, käytetään lat ja säteen kanssa
`bbox`	No	Maantieteellinen haku rajoitettu suorakulmiolla. Muoto: minLat,minLon,maxLat,maxLon.
`sort`	No	Tarjousten järjestys. Oletus on price_asc
`limit`	No	Tarjottavien määrä, esimerkiksi 5, 10. Oletus 1
`adults`	No	Aikuisten määrä 12-99 vuotta, oletus 2
`fields`	No	Kentät, jotka on sisällytettävä hakutuloksiin
`radius`	No	Säde kilometreinä lat, lon
`rating`	No	Vähimmäismäärä tähtiä, esimerkiksi 3, 4, 5
`infants`	No	Vauvojen määrä 0-1 vuotta, oletus 0
`category`	No	Loman kategoria SUNBATH=Aurinko ja uiminen, CITY=Kaupunkiloma, SKI=Hiihtoloma, EXOTIC=Eksoottinen
`children`	No	Lasten määrä 2-11 vuotta, oletus 0
`days_max`	No	Maksimimäärä päiviä lomalle, esimerkiksi 3, 7, 14
`days_min`	No	Vähimmäismäärä päiviä lomalle, esimerkiksi 3, 7, 14
`features`	No	Hotellin mukavuudet: ac=ilmastointi, adultsonly=Vain aikuisille, apartment=huoneisto, bar=baari, childspool=lastenallas, gym=kuntosali, heatedpool=lämmitetty uima-allas, kidsclub=lastenkerho, pool=uima-allas, seaview=merinäköala, restaurant=ravintola, spa=kylpylä
`max_price`	No	Maksimihinta koko matkalle, esimerkiksi 5000, 10000, 15000
`board_type`	No	Ateriat sisältyvät hotelliin, esimerkiksi aamiainen, puolihoito, täysihoito, all inclusive
`hotel_name`	No	Hotellin nimi, esimerkiksi Riu Palace, Iberostar, Sol
`temp_water`	No	Vähimmäisodotettu veden lämpötila Celsius-asteina, esimerkiksi 20, 25
`country_iso`	No	ISO-koodi maa, esimerkiksi ES, GR, PL, TR
`guest_rating`	No	Vähimmäisarvio, esimerkiksi 8.2, 9.0. Mediaani: 8.4
`direct_flight`	No	Aseta true löytääksesi hotelleja suorilla lennoilla
`distance_beach`	No	Maksimaalinen etäisyys rannalle metreinä, esimerkiksi 0, 100, 500
`depart_date_max`	No	Viimeisin mahdollinen loma-ajan alkamispäivä (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`depart_date_min`	No	Aikaisin mahdollinen loma-ajan alkamispäivä (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`distance_centre`	No	Maksimaalinen etäisyys keskustaan metreinä, esimerkiksi 0, 100, 500
`return_date_max`	No	Viimeisin mahdollinen kotiinpaluupäivä (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`return_date_min`	No	Aikaisin mahdollinen kotiinpaluupäivä (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`destination_name`	No	Kohdenimi, esimerkiksi Malta, Magaluf, Gran Canaria
`distance_airport`	No	Maksimaalinen etäisyys hotellin ja lentokentän välillä km, esimerkiksi 20, 40, 80
`number_of_nights`	No	Tarkka määrä öitä lomalle, esimerkiksi 3, 7, 14
`temp_air_day_max`	No	Maksimiodotettu päivälämpötila Celsius-asteina, esimerkiksi 25, 30
`temp_air_day_min`	No	Vähimmäisodotettu päivälämpötila Celsius-asteina, esimerkiksi 20, 25
`depart_date_exact`	No	Loman on alkaa tänä päivänä (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`return_date_exact`	No	Kotiinpaluupäivä alkaa tänä päivänä (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`origin_airport_code`	No	IATA-koodi lähtöpaikalle, esimerkiksi HEL, OUL, TLL
`destination_airport_code`	No	IATA-koodi määränpää lentokentälle, esimerkiksi ALC, AGP, TFS

Output Schema

Name	Required	Description
`results`	No

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds that results carry live prices, availability, hotel data and booking links, plus the Finland-origin scope, but says nothing about result volume, rate limits or pagination behavior.

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

Conciseness3/5

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

The core purpose is front-loaded in the first sentence, but the third sentence ('Etsi saatavilla olevia pakettimatkoja Suomesta hakukriteerien perusteella') restates the first almost verbatim and earns nothing. Roughly a third of the text is redundant.

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

Completeness3/5

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

With 37 optional parameters, a rich output schema and full annotation coverage, the description covers the essentials without needing to explain return values. However, for a tool this broad it should at least state how it relates to search_flights and whether geographic filters (lat/lon/radius vs bbox vs destination_name) can be combined.

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% across all 37 parameters, so the schema carries full documentation of enums, ranges and formats. The description contributes no parameter-level meaning beyond restating that results match search criteria; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: search available package holidays that bundle flights and accommodation and depart from Finland. The 'includes flights and accommodation' phrasing implicitly distinguishes it from the flight-only sibling search_flights, but never names that sibling.

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

Usage Guidelines3/5

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

Usage is only implied by the resource type – an agent can infer this is for package trips rather than standalone flights. There is no explicit when-to-use/when-not guidance, no mention of search_flights, and no note on how to combine the many optional filters or which are mutually exclusive.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updateNov 2, 2026

Changedsearch_holidays2 fields changed

changedInput schema / properties / fields / default

Previous value: -[
-  "origin_airport_code",
-  "features_text",
-  "rating",
-  "distance_centre",
-  "return_date",
-  "price_per_pers",
-  "temp_water",
-  "supplier_name",
-  "origin_airport_name",
-  "distance_airport",
-  "destination_airport_name",
-  "offer_id",
-  "features",
-  "url",
-  "room_type",
-  "currency",
-  "departure_date",
-  "categories",
-  "temp_air_day",
-  "hotel_name",
-  "destination_name",
-  "distance_beach",
-  "number_of_nights",
-  "hotel_image",
-  "supplier_logo",
-  "hotel_description",
-  "total_price",
-  "guest_rating",
-  "country_name",
-  "lat",
-  "lon",
-  "destination_airport_code",
-  "country_code"
-]New value: +[
+  "country_name",
+  "return_date",
+  "offer_id",
+  "destination_airport_code",
+  "temp_air_day",
+  "destination_airport_name",
+  "features",
+  "distance_centre",
+  "origin_airport_code",
+  "supplier_logo",
+  "supplier_name",
+  "country_code",
+  "hotel_description",
+  "destination_name",
+  "distance_beach",
+  "origin_airport_name",
+  "temp_water",
+  "departure_date",
+  "currency",
+  "hotel_image",
+  "price_per_pers",
+  "hotel_name",
+  "guest_rating",
+  "url",
+  "lon",
+  "room_type",
+  "categories",
+  "features_text",
+  "lat",
+  "total_price",
+  "number_of_nights",
+  "rating",
+  "distance_airport"
+]