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 with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 99.9% over 36 days
Last Tested: 2026-09-22 17:29
Transport: Streamable HTTP · MCP 2025-06-18
URL

TDQS

A3.6/5.0

Scored 2026-09-22 16:35 across 2 tools

Disambiguation5/5

The two tools are clearly distinct: search_flights handles only flight bookings, while search_holidays covers package holiday deals. There is no overlap in purpose or functionality, making agent selection unambiguous.

Naming Consistency5/5

Both tools follow the same 'search_' verb_noun pattern with descriptive nouns ('flights', 'holidays'). The naming is consistent, predictable, and easy to understand.

Tool Count3/5

With only two tools, the server feels thin for a general travel search domain. While the focus on flights and package holidays is coherent, one might expect additional search categories (e.g., hotels, car rentals). It sits at the low end of acceptable but not extremely sparse.

Completeness3/5

The tool surface only provides search operations—no capabilities for retrieving specific offers, booking, or managing reservations. For a travel search server, basic search is covered but the absence of supplementary operations (e.g., get_flight_details, book_holiday) leaves notable gaps. However, given the server's stated purpose as a search layer, it's minimally acceptable but not comprehensive.

Available Tools

2 tools

search_flightsEtsi lentotarjouksia SuomestaA

Read-only

Inspect

NDC-yhteensopiva API lentojen (vain lennot) hakuun Suomesta. Tietokanta sisältää tilauslentojen paikkoja, joita ei yleensä löydy Google Flightsista, Skyscanneristä tai Kayakista. Etsi parhaat saatavilla olevat lentotarjoukset hakukriteerien perusteella.

ParametersJSON Schema

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)

TDQS

A3.9/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, covering the safety profile. The description adds useful context about NDC compatibility and the unique charter inventory, but does not disclose operational details such as response format, rate limits, or search completeness behavior.

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 three short sentences with no wasted words. It front-loads the core function, adds differentiating inventory context, and closes with the expected outcome of finding the best available flight deals.

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 17 parameters and no output schema, the description provides the core purpose and data-source differentiator but does not explain result structure, pagination, or what constitutes a valid minimal query. The schema covers parameters well, but the description alone does not fully equip an agent to understand all behavior of a complex search tool.

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 the schema already documents every parameter. The description adds no parameter-level detail beyond a generic reference to 'search criteria', which is appropriate for the baseline but provides no additional semantic value.

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 states a specific verb and resource: a flight search API for flights only from Finland. It also distinguishes itself from the sibling search_holidays by emphasizing 'vain lennot' (flights only) and by highlighting charter inventory not available on other travel search engines.

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?

The description gives clear context for when to use the tool: when searching for flights, especially charter flight seats not found on mainstream search engines. It does not explicitly name an alternative or state 'use search_holidays for holiday packages', but the 'vain lennot' phrasing strongly implies the boundary.

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 SuomestaA

Read-only

Inspect

API hakuun suurimmasta ja kattavimmasta tietokannasta Suomessa pakettimatkojen tarjouksista. API:ta käytetään antamaan parhaat tarjoukset pakettimatkoista, jotka tarjoavat Tjäreborg, TUI, Apollo, Nazar, Ticket ja monet muut. Etsi parhaat saatavilla olevat pakettimatkat Suomesta hakukriteerien perusteella.

ParametersJSON Schema

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

TDQS

A3.6/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, and the description does not contradict them. The description adds useful scope context—Finnish market, specific tour operators, and 'best offers' intent—but provides no additional behavioral details such as result limits, pagination, or open-ended result-set behavior.

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 short and front-loaded with the resource and purpose. However, the second sentence largely restates the first ('API search' vs. 'API is used to provide offers'), so there is minor redundancy despite the compact size.

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?

Given the tool's complexity—37 optional parameters, no output schema, and a flight-search sibling—the description gives only high-level domain context. It omits guidance on result shape, default behavior, or when to prefer this tool over search_flights, leaving the agent to rely entirely on the schema and annotations.

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 37 parameters are already documented in the schema. The description only refers generically to 'hakukriteerien perusteella' and adds no parameter-level meaning beyond what the schema provides.

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 states a specific action—searching package-tour deals—against a named resource: Finland's largest and most comprehensive package-holiday database. It also names the major suppliers covered, which makes the tool's scope concrete and clearly distinct from the sibling search_flights.

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?

The description implies the use case: it is for finding package-tour offers from Finnish suppliers based on search criteria. However, it never explicitly distinguishes this from search_flights, states when not to use it, or names alternatives, leaving the agent to infer routing.

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 updateSep 22, 2026

Changedsearch_holidays2 fields changed

changedInput schema / properties / fields / default

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