Restplass travel search

Server Details

Realtime package holiday and charter flight prices from Norway. 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 57 days
Last Tested: 2026-10-13 11:59
Transport: Streamable HTTP · MCP 2025-06-18
URL

TDQS

A3.6/5.0

Scored 2026-10-08 07:07 across 2 tools

Disambiguation5/5

The two tools target clearly different resources: flights versus package holidays. Their descriptions explicitly distinguish charter flight inventory from bundled holiday offers, leaving no realistic chance of misselection.

Naming Consistency5/5

Both tools use the same search_<noun> pattern: search_flights and search_holidays. The convention is fully consistent and predictable.

Tool Count3/5

Two tools is borderline thin for a travel search server. While the scope may be search-only, there is little room for ancillary operations like airport lookup, date flexibility, or offer details.

Completeness3/5

The surface covers flight and package-holiday search, but has notable gaps: no retrieval of specific offer details, no booking/lifecycle operations, and no supporting lookup tools. Agents can search but may hit dead ends beyond initial results.

Available Tools

2 tools

search_flightsSøk etter flytilbud fra NorgeA

Read-only

Inspect

NDC-justert API for å søke etter flyreiser (kun fly) tilgjengelig fra Norge. Databasen inneholder seter på charterfly som vanligvis ikke finnes hos Google Flights, Skyscanner eller Kayak. Finn de beste tilgjengelige flytilbudene basert på søkekriterier.

ParametersJSON Schema

Name	Required	Description	Default
`adt`	No	Antall voksne (NDC: PaxType=ADT), default 1
`chd`	No	Antall barn (NDC: PaxType=CHD), default 0
`inf`	No	Antall spedbarn (NDC: PaxType=INF), default 0
`dest`	No	IATA kode for destinasjonsflyplass, f.eks. AYT, AGP, TFS
`orig`	No	IATA kode for avreiseflyplass, f.eks. OSL, SVG, TRD
`sort`	No	Sorteringsrekkefølge, default price_asc	price_asc
`limit`	No	Antall tilbud som returneres (1-25), default 10
`direct`	No	Kun direktefly (NDC: StopQuantity=0)
`dep_date`	No	Eksakt utreisedato (YYYY-MM-DD)
`ret_date`	No	Eksakt returdato (YYYY-MM-DD)
`max_price`	No	Maksimum totalpris (NDC: PriceRangeFilter.MaxAmount)
`nights_max`	No	Maksimum antall netter (vendor extension, ikke NDC)
`nights_min`	No	Minimum antall netter (vendor extension, ikke NDC)
`dep_date_to`	No	Seneste utreisedato (YYYY-MM-DD)
`ret_date_to`	No	Seneste returdato (YYYY-MM-DD)
`dep_date_from`	No	Tidligste utreisedato (YYYY-MM-DD)
`ret_date_from`	No	Tidligste returdato (YYYY-MM-DD)

Output Schema

ParametersJSON Schema

Name	Required	Description
`total`	No
`offers`	No

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds context about NDC alignment and the unique charter inventory, which is useful but not behavioral in the sense of side effects or response handling. It does not describe output structure or pagination, but given the output schema exists and annotations cover the safety profile, this is acceptable.

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?

The description is three sentences, each carrying relevant information: the core purpose, the unique value proposition (charter inventory), and the result orientation. It is front-loaded with the most important details and contains no filler or repetition.

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

Completeness4/5

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

Given the tool has 17 parameters but 100% schema coverage, an output schema, and annotations covering safety, the description provides adequate context. It clarifies the geographical scope (from Norway) and the niche (charter seats), which are not in the schema. It does not explain when to use date ranges vs exact dates, but that is implicitly in the schema. Overall, it is complete enough for an agent to invoke correctly.

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%, meaning every parameter is already documented in the input schema. The description only generically mentions 'søkekriterier' (search criteria) without adding specific parameter semantics beyond what the schema provides. Since the schema fully covers parameters, 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 clearly states the tool's purpose: to search for flight offers (flights only) available from Norway. The verb 'søke' (search) is specific, and the resource is well-defined. It explicitly differentiates from the sibling 'search_holidays' by emphasizing 'kun fly' (flights only), so an agent can distinguish them without opening 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 Guidelines3/5

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

The description implies usage context by noting it covers charter flights not found on major booking sites and is limited to flights from Norway. However, it does not explicitly mention when to use this tool versus the sibling 'search_holidays' or when not to use it. The guidance is implied rather than explicit, so it earns a mid-range score.

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

search_holidaysSøk etter restplasser og pakkereisetilbud fra Norge

Read-only

Inspect

Søk etter tilgjengelige pakkereiser inkludert fly og overnatting med avreise fra Norge. Returnerer gjeldende priser, tilgjengelighet, hotellinformasjon og bestillingslenker som samsvarer med brukerens søkekriterier. Finn de beste tilgjengelige pakkereisetilbudene fra Norge basert på søkekriterier.

ParametersJSON Schema

Name	Required	Description
`lat`	No	Breddegrad i desimalgrader, brukes med lon og radius
`lon`	No	Lengdegrad i desimalgrader, brukes med lat og radius
`bbox`	No	Geografisk søk avgrenset med et rektangel. Format: minLat,minLon,maxLat,maxLon.
`sort`	No	Sorteringsrekkefølge for tilbudene. Default er price_asc
`limit`	No	Antall tilbud som skal returneres, for eksempel 5, 10. Default 1
`adults`	No	Antall voksne 12-99 år, default 2
`fields`	No	Felt som skal inkluderes i søkeresultatet
`radius`	No	Radius i kilometer fra lat, lon
`rating`	No	Minimum antall stjerner, for eksempel 3, 4, 5
`infants`	No	Antall spedbarn 0-1 år, default 0
`category`	No	Kategori for ferien SUNBATH=Syden,Sol&bad, CITY=storbyferie, SKI=skiferie, EXOTIC=fjerne strender
`children`	No	Antall barn 2-11 år, default 0
`days_max`	No	Maksimum antall dager for ferien, for eksempel 3, 7, 14
`days_min`	No	Minimum antall dager for ferien, for eksempel 3, 7, 14
`features`	No	Fasiliteter på hotellet: ac=aircondition, adultsonly=Kun for voksne, apartment=leilighet, bar=bar, childspool=barnepool, gym=treningssenter, heatedpool=oppvarmet basseng, kidsclub=barnklubb, pool=basseng, seaview=havutsikt, restaurant=restaurant, spa=spa
`max_price`	No	Maksimum totalpris for hele reisen, for eksempel 5000, 10000, 15000
`board_type`	No	Måltider inkludert på hotellet, f.eks frokost, halvpensjon, helpensjon, all inclusive
`hotel_name`	No	Hotellnavn, for eksempel Riu Palace, Iberostar, Sol
`temp_water`	No	Minimum forventet vanntemperatur i Celsius, for eksempel 20, 25
`country_iso`	No	ISO kode for land, for eksempel ES, GR, PL, TR
`guest_rating`	No	Minimum gjestevurdering, for eksempel 8.2, 9.0. Median: 8.4
`direct_flight`	No	Sett til true for å finne hoteller med direktefly
`distance_beach`	No	Maksimal avstand til stranden i meter, for eksempel 0, 100, 500
`depart_date_max`	No	Seneste mulige start på ferien (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`depart_date_min`	No	Tidligste mulige start på ferien (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`distance_centre`	No	Maksimal avstand til sentrum i meter, for eksempel 0, 100, 500
`return_date_max`	No	Seneste mulige hjemreise (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`return_date_min`	No	Tidligste mulige hjemreise (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`destination_name`	No	Destinasjonsnavn, for eksempel Malta, Magaluf, Gran Canaria
`distance_airport`	No	Maksimal avstand melom hotell og flyplass i km, for eksempel 20, 40, 80
`number_of_nights`	No	Eksakt antall netter for ferien, for eksempel 3, 7, 14
`temp_air_day_max`	No	Maksimum forventet dagtemperatur i Celsius, for eksempel 25, 30
`temp_air_day_min`	No	Minimum forventet dagtemperatur i Celsius, for eksempel 20, 25
`depart_date_exact`	No	Ferien skal starte denne dagen (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`return_date_exact`	No	Hjemreisen skal begynner denne dagen(ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`origin_airport_code`	No	IATA kode for avreiseflyplass, for eksempel OSL, SVG, TRD
`destination_airport_code`	No	IATA kode for destinasjonsflyplass, for eksempel ALC, AGP, TFS

Output Schema

ParametersJSON Schema

Name	Required	Description
`results`	No

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updateOct 13, 2026

Changedsearch_holidays2 fields changed

changedInput schema / properties / fields / default

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