Afbudsrejser travel search

Server Details

Realtime package holiday and charter flight prices from Denmark. 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
Last Tested: 2026-09-20 22:20
Transport: Streamable HTTP · MCP 2025-06-18
URL

TDQS

A3.8/5.0

Scored 2026-09-20 21:45 across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one searches for flights only and the other searches for package holidays. There is no ambiguity about which tool to select for a given query.

Naming Consistency5/5

Both tools follow the same 'search_' prefix followed by the resource type, creating a perfectly consistent and predictable naming pattern.

Tool Count4/5

Two tools is on the low end, but it is appropriate for a focused travel search server that covers the two primary product categories: flights and package holidays. The small count keeps the surface clear without unnecessary overhead.

Completeness4/5

The server covers the core search needs for its domain: flights and package holidays. It lacks additional travel products like hotel-only or car rental searches, but these are arguably outside the stated purpose of a holiday travel search API.

Available Tools

2 tools

search_flightsSøg efter flytilbud fra DanmarkA

Read-only

Inspect

NDC-justeret API til at søge efter flyrejser (kun fly) tilgængelige fra Danmark. Databasen indeholder sæder på charterfly, som normalt ikke findes hos Google Flights, Skyscanner eller Kayak. Find de bedste tilgængelige flytilbud baseret på søgekriterier.

ParametersJSON Schema

Name	Required	Description	Default
`adt`	No	Antal voksne (NDC: PaxType=ADT), default 1
`chd`	No	Antal børn (NDC: PaxType=CHD), default 0
`inf`	No	Antal spædbørn (NDC: PaxType=INF), default 0
`dest`	No	IATA kode for destinationslufthavn, f.eks. AYT, AGP, TFS
`orig`	No	IATA kode for afrejselufthavn, f.eks. CPH, BLL, AAL
`sort`	No	Sorteringsrækkefølge, default price_asc	price_asc
`limit`	No	Antal tilbud (1-25), default 10
`direct`	No	Kun direkte fly (NDC: StopQuantity=0)
`dep_date`	No	Eksakt afrejsedato (YYYY-MM-DD)
`ret_date`	No	Eksakt returdato (YYYY-MM-DD)
`max_price`	No	Maksimal totalpris (NDC: PriceRangeFilter.MaxAmount)
`nights_max`	No	Maksimum antal nætter (vendor extension, ikke NDC)
`nights_min`	No	Minimum antal nætter (vendor extension, ikke NDC)
`dep_date_to`	No	Seneste afrejsedato (YYYY-MM-DD)
`ret_date_to`	No	Seneste returdato (YYYY-MM-DD)
`dep_date_from`	No	Tidligste afrejsedato (YYYY-MM-DD)
`ret_date_from`	No	Tidligste returdato (YYYY-MM-DD)

TDQS

A4/5.0

Behavior4/5

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

Annotations already mark the operation as read-only and non-destructive. The description adds context beyond annotations by revealing this is an NDC-based API with charter-flight inventory not available on mainstream OTAs, which helps set expectations about result uniqueness and source.

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, with the core scope in the first sentence and valuable data-source context in the second. The final sentence is somewhat redundant with the first but the overall description remains tight and well-structured.

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?

Given the tool has 17 optional parameters and no output schema, the description does not explain parameter interactions (e.g., exact dates vs. date ranges) or what the response structure looks like. It is adequate for basic selection but leaves important invocation details to inference.

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%, with all 17 parameters already documented with defaults, formats, examples, and NDC mappings. The description adds no additional parameter-level meaning beyond the generic 'based on search criteria,' so the schema does the heavy lifting.

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 uses a specific verb and resource ('søge efter flyrejser') and explicitly scopes it to flights from Denmark. The phrase 'kun fly' separates it from the sibling search_holidays, and the charter-flight inventory detail further defines what kind of offers are returned.

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 clearly signals this tool is for flight-only searches from Denmark, which implies the alternative search_holidays covers broader holiday packages. However, it does not explicitly name the sibling or state conditions like 'use this when the user wants flights only and search_holidays when they want packages.'

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

search_holidaysSøg efter afbudsrejser og pakkerejser fra Danmark

Read-only

Inspect

API til at søge i den største og mest komplette database i Danmark efter pakkerejsetilbud. API'et bruges til at give de bedste tilbud på pakkerejser, der tilbydes af Spies, TUI, Apollo, Nazar, Ticket, Solfaktor og mange andre. Find de bedste tilgængelige pakkerejser fra Danmark baseret på søgekriterier.

ParametersJSON Schema

Name	Required	Description
`lat`	No	Breddegrad i decimalgrader, bruges med lon og radius
`lon`	No	Længdegrad i decimalgrader, bruges med lat og radius
`bbox`	No	Geografisk søgning begrænset med en rektangel. Format: minLat,minLon,maxLat,maxLon.
`sort`	No	Sorteringsrækkefølge for tilbuddene. Standard er price_asc
`limit`	No	Antal tilbud, der skal returneres, for eksempel 5, 10. Standard 1
`adults`	No	Antal voksne 12-99 år, default 2
`fields`	No	Felter, der skal inkluderes i søgeresultatet
`radius`	No	Radius i kilometer fra lat, lon
`rating`	No	Minimum antal stjerner, for eksempel 3, 4, 5
`infants`	No	Antal spædbørn 0-1 år, default 0
`category`	No	Kategori for ferien SUNBATH=Sol og bad, CITY=Storbyferie, SKI=Skiferie, EXOTIC=Eksotisk
`children`	No	Antal børn 2-11 år, default 0
`days_max`	No	Maksimalt antal dage for ferien, for eksempel 3, 7, 14
`days_min`	No	Minimum antal dage for ferien, for eksempel 3, 7, 14
`features`	No	Faciliteter på hotellet: ac=aircondition, adultsonly=Kun for voksne, apartment=lejlighed, bar=bar, childspool=børnepool, gym=træningscenter, heatedpool=opvarmet pool, kidsclub=børneklub, pool=pool, seaview=havudsigt, restaurant=restaurant, spa=spa
`max_price`	No	Maksimal totalpris for hele rejsen, for eksempel 5000, 10000, 15000
`board_type`	No	Måltider inkluderet på hotellet, for eksempel morgenmad, halvpension, helpension, all inclusive
`hotel_name`	No	Hotelnavn, for eksempel Riu Palace, Iberostar, Sol
`temp_water`	No	Minimum forventet vandtemperatur i Celsius, for eksempel 20, 25
`country_iso`	No	ISO-kode for land, for eksempel ES, GR, PL, TR
`guest_rating`	No	Minimum gæstevurdering, for eksempel 8.2, 9.0. Median: 8.4
`direct_flight`	No	Sæt til true for at finde hoteller med direktefly
`distance_beach`	No	Maksimal afstand til stranden i meter, for eksempel 0, 100, 500
`depart_date_max`	No	Senest mulige start på ferien (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`depart_date_min`	No	Tidligst mulige start på ferien (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`distance_centre`	No	Maksimal afstand til centrum i meter, for eksempel 0, 100, 500
`return_date_max`	No	Senest mulige hjemreise (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`return_date_min`	No	Tidligst mulige hjemreise (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`destination_name`	No	Destinationsnavn, for eksempel Malta, Magaluf, Gran Canaria
`distance_airport`	No	Maksimal afstand mellem hotel og lufthavn i km, for eksempel 20, 40, 80
`number_of_nights`	No	Præcis antal nætter 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 afrejselufthavn, for eksempel CPH, BLL, AAL
`destination_airport_code`	No	IATA kode for destination lufthavn, for eksempel ALC, AGP, TFS

Tool Schema Changelog

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

1 tool updateSep 20, 2026

Changedsearch_holidays2 fields changed

changedInput schema / properties / fields / default

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