Akkilahdot travel search

Etsi lentotarjouksia Suomesta

search_flights

Read-only

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.

Input 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)

Output Schema

Name	Required	Description	Default
`total`	No
`offers`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "offers": {
+      "items": {
+        "properties": {
+          "offer_id": {
+            "type": "string"
+          },
+          "origin_destinations": {
+            "items": {
+              "properties": {
+                "arrival": {
+                  "properties": {
+                    "airport_code": {
+                      "type": "string"
+                    },
+                    "datetime": {
+                      "format": "date-time",
+                      "type": "string"
+                    }
+                  },
+                  "type": "object"
+                },
+                "departure": {
+                  "properties": {
+                    "airport_code": {
+                      "type": "string"
+                    },
+                    "datetime": {
+                      "format": "date-time",
+                      "type": "string"
+                    }
+                  },
+                  "type": "object"
+                },
+                "flight_numbers": {
+                  "items": {
+                    "type": "string"
+                  },
+                  "type": "array"
+                },
+                "stop_quantity": {
+                  "type": "integer"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "supplier": {
+            "type": "string"
+          },
+          "total_price": {
+            "properties": {
+              "amount": {
+                "type": "integer"
+              },
+              "currency_code": {
+                "type": "string"
+              },
+              "per_pax_amount": {
+                "type": "integer"
+              }
+            },
+            "type": "object"
+          },
+          "trip_duration_nights": {
+            "description": "Öiden määrä (vendor extension, ei standardi NDC)",
+            "type": "integer"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedJul 16, 2026

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.

All Akkilahdot travel search tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?