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 by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 99.9% over 76 days
Last Tested: 2026-11-07 19:35
Transport: Streamable HTTP · MCP 2025-06-18
URL
ChatGPT: –
Claude: –

TDQS

A3.9/5.0

Scored 2026-11-07 19:50 across 2 tools

Disambiguation5/5

The two tools target clearly distinct products: flight-only charter seats versus flight+accommodation package holidays. The descriptions explicitly cross-reference each other ('För flyg och hotell, använd search_holidays'), leaving no room for misselection.

Naming Consistency5/5

Both tools follow the same snake_case verb_noun pattern (search_flights, search_holidays) with a shared prefix that reinforces the search domain. Fully predictable naming.

Tool Count3/5

Two tools is thin for a travel search surface; the server covers only two product shapes and offers no ambient lookups. It is not egregiously wrong for a scoped search service, but it sits at the borderline the rubric calls thin.

Completeness3/5

Core search for both product types is covered and results include prices, availability, and booking links, but there is no hotel-only search, no destination/departure-airport lookup, and no way to fetch details for a specific offer. These are notable gaps agents will hit when refining or drilling into results.

Available Tools

2 tools

search_flightsSök efter flygerbjudanden från SverigeA

Read-only

Inspect

Sök i realtid efter charterflyg (endast flyg) från sistaminuten.se. Använd vid förfrågningar om flyg utan boende, t.ex. 'endast flyg', 'flygstol', 'charterflyg utan hotell' och 'flygbiljetter'. Returnerar tillgängliga flygerbjudanden, inte paketresor. För flyg och hotell, använd search_holidays.

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

Name	Required	Description
`total`	No
`offers`	No

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context: the search is real-time, the source is sistaminuten.se, results are available flight deals rather than package holidays. It does not discuss auth, rate limits, or pagination, but those are less critical given the annotations and output schema.

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?

Four short sentences with no wasted text. Purpose is front-loaded, followed by usage scenarios, return scope, and the sibling alternative. Every sentence contributes useful routing or scope information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, usage conditions, return scope, and the alternative tool. The schema fully documents all parameters, annotations cover safety and openness, and an output schema exists, so no essential agent-facing context is missing.

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, including defaults and IATA examples. The description does not add parameter-specific meaning beyond the schema. With full schema coverage, 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 states a specific verb and resource: real-time search for charter flights, flight-only, from sistaminuten.se. It explicitly distinguishes the result from package tours and names the sibling tool search_holidays for the package case.

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 gives explicit when-to-use guidance for flight-only requests with concrete examples ('endast flyg', 'flygstol', 'charterflyg utan hotell', 'flygbiljetter'). It also names the alternative search_holidays and the condition that selects it: flight plus hotel.

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

Sök efter tillgängliga paketresor inklusive flyg och boende med avresa från Sverige. Returnerar aktuella priser, tillgänglighet, hotellinformation och bokningslänkar som matchar användarens sökkriterier. Hitta tillgängliga paketresor från Sverige baserat på sökkriterier.

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

Output Schema

Name	Required	Description
`results`	No

TDQS

B3.4/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, so the safety profile is covered. The description adds that results carry live prices, availability, hotel details and booking links, but says nothing about result volume, pagination, or the fact that limit defaults to 1 — a behaviorally significant default left undiscussed.

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?

The first two sentences are front-loaded and informative, but the third — 'Hitta tillgängliga paketresor från Sverige baserat på sökkriterier' — only restates the opening and earns no place. The definition is in Swedish while the tool name and sibling are English, which adds a small parsing burden but no real bloat.

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?

An output schema exists and the schema documents every parameter, so the description need not explain return values in depth. However, for a 37-parameter open-world search with a default limit of 1 and five overlapping geographic filters, the description gives no guidance on constructing a sensible query, leaving a real gap for an agent new to the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% across all 37 parameters, including enum explanations, units (km, meters, Celsius) and ISO 8601 formats, so the schema carries the semantic load. The description correctly stays high-level rather than repeating it, though it adds no extra meaning of its own (e.g. how lat/lon/radius interact with bbox or destination_name).

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?

States a specific verb and resource: 'Sök efter tillgängliga paketresor inklusive flyg och boende med avresa från Sverige', and clarifies what is returned (prices, availability, hotel info, booking links). The '(inklusive flyg och boende)' clause implicitly separates it from the flight-only sibling search_flights, but the sibling is never named, so the differentiation is inferred rather than stated.

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?

Usage is only implied: the agent can infer this tool is for bundled flight+hotel trips originating in Sweden, which softly contrasts with search_flights. There is no explicit 'use this when / use X instead' routing, no mention of required search criteria, and nothing about how narrowly an agent should filter given 37 optional parameters.

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 updateNov 7, 2026

Changedsearch_holidays2 fields changed

changedInput schema / properties / fields / default

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