Akkilahdot travel search

Etsi lentotarjouksia Suomesta

search_flights

Read-only

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.

Input Schema

TableJSON 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

TableJSON 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/5.0

Behavior4/5

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

Annotations already cover read-only and open-world behavior. The description adds NDC compatibility and the fact that the underlying database contains charter seats not visible in Google Flights/Skyscanner/Kayak, which is useful behavioral/inventory context beyond the annotations.

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?

Three short sentences, with the core NDC and flights-only distinction front-loaded. The final sentence about finding deals is somewhat generic, but the description remains tight and scannable.

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?

For a 17-parameter search tool with no required fields, the description should signal that a meaningful search needs at least origin, destination, and date(s). It does not state any minimum invocation criteria, leaving that critical practical detail to inference.

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 each parameter is already documented with types, defaults, and examples. The description adds no parameter-level meaning such as required combinations or date-conflict rules; baseline 3 applies.

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 ('haku' / searching), the resource (flights), and a distinguishing scope ('vain lennot', NDC-compatible, charter inventory). The phrase 'vain lennot' separates it from the holiday sibling without needing the schema.

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?

Gives clear context: this is for flight-only searches from Finland and stresses that it covers charter seats missing from major OTAs. It does not explicitly name search_holidays as the alternative, but the 'vain lennot' exclusion makes the intended use unambiguous.

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?