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 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 55 days
Last Tested: 2026-10-11 06:15
Transport: Streamable HTTP · MCP 2025-06-18
URL

TDQS

A3.6/5.0

Scored 2026-10-08 06:45 across 2 tools

Disambiguation5/5

The two tools target clearly distinct domains: search_flights covers flight-only NDC inventory, while search_holidays covers packaged holiday deals from tour operators. An agent can unambiguously pick the right one based on whether the user wants a flight or a package.

Naming Consistency5/5

Both tools follow an identical search_<noun> verb_noun pattern in snake_case, making the set perfectly predictable.

Tool Count3/5

Only two tools for a travel search server is thin; each vertical has exactly one operation with no supporting tools like detail lookups or filtering helpers. It is functional but borderline minimal for the apparent scope.

Completeness3/5

Search coverage exists for both flights and package holidays, but there are no companion tools for offer details, availability refinement, or booking/lifecycle steps, leaving agents with dead ends once a search returns results.

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)

Output Schema

ParametersJSON Schema

Name	Required	Description
`total`	No
`offers`	No

TDQS

A3.7/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 the safety profile is fully covered and there is no contradiction with the read-only search described. Beyond the annotations, the description adds genuinely useful context: the NDC-adjusted protocol, the flight-only scope, and the unique charter-inventory source, none of which are derivable from the schema or annotations. Return-format details are largely covered by the existing output schema, so its absence is not a significant gap.

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 purpose front-loaded in the first sentence, and the second sentence earning its place by explaining the unique inventory. The final sentence ('Find de bedste tilgængelige flytilbud...') is mild boilerplate that adds little, but the overall size is appropriate for a 17-parameter tool. No redundancy or padding beyond that one filler clause.

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 complex tool with 17 parameters, the supporting structure is strong: full schema descriptions, rich annotations, and an output schema, so the description need not explain parameters or return values. It supplies the non-schema context an agent needs: Denmark-origin scope, flight-only eligibility, and the charter-inventory differentiation. It could have explicitly routed between exact-date vs. date-range parameters or named search_holidays, but nothing essential for invoking the tool correctly 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%, with all 17 parameters documented including NDC references (PaxType=ADT/CHD/INF), defaults, format (YYYY-MM-DD), and enums. Per the rubric, the baseline is 3 when the schema carries the full burden, and the description adds no parameter-level detail beyond it. The closing phrase 'Find de bedste tilgængelige flytilbud baseret på søgekriterier' merely confirms the schema's semantics rather than extending them.

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 description states a specific verb, resource, and scope: an NDC-adjusted API to search for flights ('søge efter flyrejser (kun fly) tilgængelige fra Danmark'), with the title 'Søg efter flytilbud fra Danmark' reinforcing flight-deal search from Denmark. The '(kun fly)' parenthetical implicitly distinguishes it from the holiday-package sibling, and the charter-inventory sentence positions it against Google Flights, Skyscanner, and Kayak. It stops short of naming the sibling directly, hence 4 rather than 5.

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 when this tool adds value: the database holds charter-flight seats that do not normally appear on Google Flights, Skyscanner, or Kayak, which hints at usage for hard-to-find charter inventory. However, it never explicitly names the sibling search_holidays, nor does it state when-not-to-use or which conditions route the agent to the alternative. Guidance on tool selection is left to inference.

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

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

Changedsearch_holidays2 fields changed

changedInput schema / properties / fields / default

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