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 21:37
Transport: Streamable HTTP · MCP 2025-06-18
URL
ChatGPT: –
Claude: –

TDQS

A3.6/5.0

Scored 2026-11-07 21:40 across 2 tools

Disambiguation5/5

The two tools target clearly different products: charter flights only versus package holidays including flight and accommodation. The descriptions explicitly cross-reference each other ('För flyg och hotell, använd search_holidays'), removing any risk of misselection.

Naming Consistency5/5

Both tools follow the same clean verb_noun pattern (search_flights, search_holidays) in snake_case with a shared verb. No mixed conventions or vague names.

Tool Count3/5

Two tools is borderline thin even for a search-focused server; there is no way to refine, paginate, or drill into a result. However, the narrow scope of 'last minute travel search' means each tool does earn its place.

Completeness3/5

Core search is covered for both product types, but the surface is a dead end after searching: no tool to fetch details for a specific offer, list destinations/departure airports, or filter results. Agents must work around gaps using only free-text search parameters.

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.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, so the safety profile is covered. The description adds that live prices, availability, hotel info and booking links are returned, but since an output schema exists this return information is largely redundant. No mention of pagination, result caps (limit max 25), or data freshness beyond "aktuella priser".

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 lead sentence is well front-loaded, but the third sentence repeats the first almost verbatim and earns no place. Two of three sentences could be merged, and the useful return-value detail sits behind a redundant closing line.

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 annotations, a full output schema and 100% schema coverage, the definition is adequate but thin for a 37-parameter tool whose filters interact (location vs bbox, depart_date_min/max vs exact, days vs number_of_nights). It never tells the agent that all parameters are optional or that results are capped at 25, so the agent must discover those constraints from structured fields alone.

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% across all 37 parameters, including enums with value explanations and date formats, so the schema carries full parameter semantics. The description adds no extra parameter meaning, such as how geographic filters (lat/lon/radius vs bbox) interact or how the date-range variants combine. Baseline 3 applies when the schema does all the work.

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 first sentence names a specific verb ("Sök") and resource ("paketresor inklusive flyg och boende med avresa från Sverige"), which is far more precise than the title alone. It does not name the sibling search_flights or state how package holidays differ from flight-only search, so an agent must infer the boundary rather than read it.

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?

There is no statement of when to use this tool versus search_flights, no prerequisites, and no exclusions. The final sentence merely restates the purpose in different words instead of adding routing guidance. Only the word "paketresor" implicitly signals the distinction.

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