Sistaminuten travel search

Sök efter flygerbjudanden från Sverige

search_flights

Read-only

NDC-justerat API för att söka efter flygresor (endast flyg) tillgängliga från Sverige. Databasen innehåller säten på charterflyg som vanligtvis inte hittas hos Google Flights, Skyscanner eller Kayak. Hitta de bästa tillgängliga flygerbjudandena baserat på sökkriterier.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`adt`	No	Antal vuxna (NDC: PaxType=ADT), standard 1
`chd`	No	Antal barn (NDC: PaxType=CHD), standard 0
`inf`	No	Antal spädbarn (NDC: PaxType=INF), standard 0
`dest`	No	IATA-kod för destinationsflygplats, t.ex. AYT, AGP, TFS
`orig`	No	IATA-kod för avgångsflygplats, t.ex. ARN, GOT, MMX
`sort`	No	Sorteringsordning, standard price_asc	price_asc
`limit`	No	Antal erbjudanden (1-25), standard 10
`direct`	No	Endast direktflyg (NDC: StopQuantity=0)
`dep_date`	No	Exakt avgångsdatum (YYYY-MM-DD)
`ret_date`	No	Exakt returdatum (YYYY-MM-DD)
`max_price`	No	Maximal totalpris (NDC: PriceRangeFilter.MaxAmount)
`nights_max`	No	Maximum antal nätter (vendor extension, inte NDC)
`nights_min`	No	Minimum antal nätter (vendor extension, inte NDC)
`dep_date_to`	No	Senaste avgångsdatum (YYYY-MM-DD)
`ret_date_to`	No	Senaste returdatum (YYYY-MM-DD)
`dep_date_from`	No	Tidigaste avgångsdatum (YYYY-MM-DD)
`ret_date_from`	No	Tidigaste returdatum (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": "Antal nätter (vendor extension, inte standard NDC)",
+            "type": "integer"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedJul 16, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already cover readOnlyHint=true and destructiveHint=false, so the description does not need to restate safety. It adds context about NDC adjustment and the charter-seat inventory, but it does not disclose behavior such as result limits, default date ranges, or what happens when no search criteria are supplied. There is no contradiction with 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?

The description is compact at three sentences and front-loads the main purpose. The final sentence ('Hitta de bästa tillgängliga flygerbjudandena...') is somewhat generic and could be trimmed, but overall the structure is clear and efficient.

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 optional parameters and no required fields, the description gives enough context to select the tool but not enough to invoke it confidently. It does not clarify whether an origin/destination pair is implicitly expected, how 'från Sverige' relates to the orig parameter, or whether the tool works with zero parameters. The presence of an output schema reduces the need to describe return values, but invocation guidance is still thin for a tool of this complexity.

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?

The input schema covers 100% of parameters with individual descriptions, including NDC mapping and defaults. The free-text description only refers generically to 'sökkriterier' and does not add parameter semantics beyond the schema, so the 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?

The description states a clear verb ('söka'), resource ('flygresor'), and scope ('från Sverige'), and adds a distinctive niche: charter flight seats not typically indexed by Google Flights, Skyscanner, or Kayak. It also clarifies 'endast flyg' to separate from package/holiday searches, though it does not explicitly name 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 Guidelines3/5

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

The context is reasonably clear: this is for flight-only searches, especially for charter inventory from Sweden. However, it never explicitly says when to use this versus search_holidays, nor does it provide exclusion criteria or name alternatives. The 'endast flyg' phrase implies the distinction but does not make it actionable.

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

All Sistaminuten 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?