Sistaminuten travel search

Server Details

Realtime package holiday and charter flight prices from Sweden. 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:13
Transport: Streamable HTTP · MCP 2025-06-18
URL

TDQS

A3.6/5.0

Scored 2026-09-22 17:20 across 2 tools

Disambiguation5/5

The two tools, search_flights and search_holidays, target completely different travel products (flight-only versus package holidays), so there is no ambiguity in selecting the right one.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with the search_ prefix, making the naming predictable and uniform.

Tool Count3/5

With only two tools, the server feels thin for a travel search domain, though the two categories cover the core offerings. It is borderline acceptable but leaves less room for specialized search needs.

Completeness4/5

The toolset covers the two primary travel search segments (flights and package holidays) but omits related areas such as hotels, car rentals, or combined searches, which could be considered minor gaps.

Available Tools

2 tools

search_flightsSök efter flygerbjudanden från SverigeA

Read-only

Inspect

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.

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

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint false, so the safety profile is covered. The description adds useful context about the NDC-adjusted API and the unusual charter-flight inventory, but it does not describe result format, availability behavior, or rate limits.

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 sentences, each carrying information: what the API searches, what data source it draws on, and what the user gets. It is slightly redundant with the title, but it remains compact and front-loaded.

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 tool with no output schema and no required parameters, the description does not clarify which parameters must be combined to produce a valid flight search (e.g., orig, dest, and dates). It gives good market context but leaves invocation logic to the schema.

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 all 17 parameters and defaults. The description only says results are 'based on search criteria' and adds no meaning beyond what the schema provides; baseline 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 names a concrete action and resource: 'söka efter flygresor (endast flyg) tillgängliga från Sverige' [search for flights only available from Sweden]. The explicit '(endast flyg)' and the Sweden scope distinguish it from the sibling search_holidays and from general metasearch 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?

It provides clear context: this is for flight-only charter inventory that is usually absent from Google Flights, Skyscanner, or Kayak. It does not name the sibling alternative or give an explicit when-not-to-use statement, but '(endast flyg)' plus the search_holidays sibling make the intended use reasonably clear.

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

search_holidaysSök efter sista minuten och charterresor från SverigeB

Read-only

Inspect

API för att söka i den största och mest kompletta databasen i Sverige efter paketresor. API:et används för att ge de bästa erbjudandena för paketresor som erbjuds av Ving, TUI, Apollo, Nazar, Ticket, Solfaktor och många andra. Hitta de bästa tillgängliga paketresorna från Sverige baserat på sökkriterier.

ParametersJSON Schema

Name	Required	Description
`lat`	No	Latitud i decimalgrader, används med lon och radie
`lon`	No	Longitud i decimalgrader, används med lat och radie
`bbox`	No	Geografisk sökning begränsad med en rektangel. Format: minLat,minLon,maxLat,maxLon.
`sort`	No	Sorteringsordning för erbjudandena. Standard är price_asc
`limit`	No	Antal erbjudanden som ska returneras, till exempel 5, 10. Standard 1
`adults`	No	Antal vuxna 12-99 år, default 2
`fields`	No	Fält som ska inkluderas i sökresultatet
`radius`	No	Radie i kilometer från lat, lon
`rating`	No	Minimum antal stjärnor, till exempel 3, 4, 5
`infants`	No	Antal spädbarn 0-1 år, default 0
`category`	No	Kategori för semestern SUNBATH=Sol och bad, CITY=Storstad, SKI=Skidsemester, EXOTIC=Exotisk
`children`	No	Antal barn 2-11 år, default 0
`days_max`	No	Maximalt antal dagar för semestern, till exempel 3, 7, 14
`days_min`	No	Minimum antal dagar för semestern, till exempel 3, 7, 14
`features`	No	Faciliteter på hotellet: ac=luftkonditionering, adultsonly=Endast för vuxna, apartment=lägenhet, bar=bar, childspool=barnpool, gym=gym, heatedpool=uppvärmd pool, kidsclub=barnklubb, pool=pool, seaview=havsutsikt, restaurant=restaurang, spa=spa
`max_price`	No	Maximal totalpris för hela resan, till exempel 5000, 10000, 15000
`board_type`	No	Måltider inkluderade på hotellet, till exempel frukost, halvpension, helpension, all inclusive
`hotel_name`	No	Hotellnamn, till exempel Riu Palace, Iberostar, Sol
`temp_water`	No	Minimum förväntad vattentemperatur i Celsius, till exempel 20, 25
`country_iso`	No	ISO-kod för land, till exempel ES, GR, PL, TR
`guest_rating`	No	Minimum gästbetyg, till exempel 8.2, 9.0. Median: 8.4
`direct_flight`	No	Sätt till true för att hitta hotell med direktflyg
`distance_beach`	No	Maximalt avstånd till stranden i meter, till exempel 0, 100, 500
`depart_date_max`	No	Senast möjlig start på semestern (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`depart_date_min`	No	Tidigast möjlig start på semestern (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`distance_centre`	No	Maximalt avstånd till centrum i meter, till exempel 0, 100, 500
`return_date_max`	No	Senast möjlig hemresa (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`return_date_min`	No	Tidigast möjlig hemresa (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`destination_name`	No	Destinationsnamn, till exempel Malta, Magaluf, Gran Canaria
`distance_airport`	No	Maximalt avstånd mellan hotell och flygplats i km, till exempel 20, 40, 80
`number_of_nights`	No	Exakt antal nätter för semestern, till exempel 3, 7, 14
`temp_air_day_max`	No	Maksimum förväntad dagstemperatur i Celsius, till exempel 25, 30
`temp_air_day_min`	No	Minimum förväntad dagstemperatur i Celsius, till exempel 20, 25
`depart_date_exact`	No	Semestern ska börja denna dag (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`return_date_exact`	No	Hemresan ska börja denna dag (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`origin_airport_code`	No	IATA kod för avreseflygplats, till exempel ARN, GOT, MMX
`destination_airport_code`	No	IATA kod för destination flygplats, till exempel ALC, AGP, TFS

TDQS

B3.1/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 some useful context beyond that, naming the aggregated suppliers (Ving, TUI, Apollo, Nazar, Ticket, Solfaktor) and confirming the Sweden-market scope, but it discloses nothing about result freshness, real-time availability, pagination, or what 'best offers' means operationally.

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?

Three sentences with the core purpose front-loaded in the first sentence is reasonable. However, sentences two and three are largely redundant marketing language ('ge de bästa erbjudandena', 'största och mest kompletta databasen') that could be trimmed without losing information.

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 37-parameter tool with no output schema, the description is thin but the schema is exceptionally rich, and the 'fields' parameter implicitly defines the output shape. The description does establish market scope (Sweden) and supplier coverage, but it omits practical details an agent would want, such as what the default response contains, whether results are live or cached, and that the 'url' field likely points to a supplier booking page.

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% — every one of the 37 parameters is documented with descriptions, examples, defaults, and constraints. The description text itself adds no parameter-level meaning, so per the baseline for high coverage, a 3 is appropriate.

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 names a specific verb and resource: an API to search Sweden's package-trip database (paketresor), which is clearly distinct from the sibling search_flights since it covers full package holidays from multiple tour operators. The title reinforces this with 'sista minuten och charterresor från Sverige'. It does not explicitly contrast with search_flights, which keeps it from a 5.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus search_flights, nor any when-not-to-use conditions or exclusions. Usage is only inferable from the purpose statement itself ('find package trips from Sweden based on search criteria'), with no mention of alternatives or scenarios where a different tool would be appropriate.

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