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 77 days
Last Tested: 2026-11-02 19:36
Transport: Streamable HTTP · MCP 2025-06-18
URL

TDQS

A4/5.0

Scored 2026-11-02 19:45 across 2 tools

Disambiguation5/5

The two tools target clearly separate products: flight-only charter seats versus flight+accommodation package holidays. The descriptions explicitly cross-reference each other ('For fly og hotell, bruk search_holidays'), leaving no room for misselection.

Naming Consistency5/5

Both tools follow the identical search_<resource> snake_case pattern (search_flights, search_holidays). Fully predictable and readable.

Tool Count3/5

Only two tools exist, which is thin even for a narrow search service; a travel search domain typically supports more query shapes. The two present are well-scoped and non-redundant, but the surface feels minimal.

Completeness3/5

The two main product types (flight-only and package) are covered, but there is no hotel-only/accommodation search, no destination or departure-airport lookup, and no tool to fetch details or pricing calendars for a specific offer. Agents can answer the core query but hit dead ends on adjacent requests.

Available Tools

2 tools

search_flightsSøk etter flytilbud fra NorgeA

Read-only

Inspect

Søk i sanntid etter charterflytilbud (kun fly) fra restplass.no. Bruk ved forespørsler om fly uten overnatting, f.eks. 'kun fly', 'flysete', 'charterfly uten hotell' og 'flybilletter'. Returnerer tilgjengelige flytilbud, ikke pakkereiser. For fly og hotell, bruk search_holidays.

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

Name	Required	Description
`total`	No
`offers`	No

TDQS

A4.3/5.0

Behavior4/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 safety is covered. The description adds useful behavior beyond that: results are real-time, sourced from restplass.no, and contain flight offers rather than package holidays. It does not mention pagination, result volume behaviour, or rate limits, so it stops short of a 5.

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?

Four short, front-loaded sentences that put purpose and the flight-only constraint first, followed by the sibling alternative. Slight redundancy between "(kun fly)" and "Returnerer tilgjengelige flytilbud, ikke pakkereiser", which keeps it from a 5.

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?

For a 17-parameter, zero-required search tool with an output schema and rich annotations, the description covers purpose, scope, triggers, and the sibling boundary. What it omits (date-range vs exact-date interplay, sorting defaults) is already fully specified in the schema, so nothing critical 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 all 17 parameters, their defaults, ranges, and NDC mappings are already documented. The description adds no parameter guidance at all (e.g. it never clarifies when to use dep_date vs dep_date_from/to or how nights_* interacts with ret_date), so the baseline 3 applies.

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?

States a specific verb ("Søk"), resource ("charterflytilbud (kun fly)"), and source (restplass.no), plus scope restriction to flight-only. It explicitly contrasts with the sibling search_holidays, so an agent can distinguish the two without opening a schema.

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?

Gives concrete trigger phrases ("kun fly", "flysete", "charterfly uten hotell", "flybilletter") and names the alternative for the flight+hotel case: "For fly og hotell, bruk search_holidays." Both when-to-use and when-to-use-something-else are covered.

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 NorgeA

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 tilgjengelige pakkereisetilbud fra Norge basert på søkekriterier.

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

Name	Required	Description
`results`	No

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare this as a safe, read-only, open-world search, and the description adds useful context about return content: current prices, availability, hotel information, and booking links. It does not add much beyond annotations regarding rate limits or pagination, but the return-content disclosure is a meaningful extra.

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 short and front-loads the core purpose. The final sentence largely repeats the first sentence's message, making it slightly redundant, but there is no bloat beyond that.

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 37 parameters, 100% schema coverage, annotations, and an output schema, the description covers the essential purpose and return content adequately. It could more explicitly distinguish package searches from flight-only searches, but no critical information for invocation 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% across 37 parameters, so the schema already documents every parameter extensively. The description only refers generally to 'søkekriterier' and does not add syntax, defaults, or filtering semantics beyond what the schema provides.

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: searching available package tours including flight and accommodation with departure from Norway. It also distinguishes the offer type from the sibling search_flights by emphasizing bundles rather than standalone flights.

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 use case is implied by 'pakkereiser inkludert fly og overnatting med avreise fra Norge', so an agent can infer this is for package holidays. However, the description never explicitly says when to use this instead of search_flights, nor does it name any exclusions or prerequisites.

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

Changedsearch_holidays2 fields changed

changedInput schema / properties / fields / default

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