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

TDQS

A3.7/5.0

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

Disambiguation5/5

The two tools target clearly distinct product types: flight-only versus package holidays with accommodation. Descriptions explicitly cross-reference when to use the other tool, eliminating ambiguity.

Naming Consistency5/5

Both tools follow the same search_<plural_noun> convention. Perfectly predictable pattern.

Tool Count3/5

Two tools is thin for a travel search server; even a narrowly scoped product likely needs a hotel-only search or destination lookup. It is borderline rather than clearly appropriate.

Completeness4/5

Flight-only and package holiday search are covered with prices, availability and booking links. Minor gap: no standalone hotel-only search or destination/date browsing, though agents can work around this.

Available Tools

2 tools

search_flightsSøg efter flytilbud fra DanmarkA

Read-only

Inspect

Søg i realtid efter charterflytilbud (kun fly) fra afbudsrejser.dk. Brug ved forespørgsler om fly uden overnatning, f.eks. 'kun fly', 'flysæde', 'charterfly uden hotel' og 'flybilletter'. Returnerer tilgængelige flytilbud, ikke pakkerejser. For fly og hotel, brug search_holidays.

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

Name	Required	Description
`total`	No
`offers`	No

TDQS

A4.4/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 and external reach are covered. The description adds real value beyond that by disclosing that results are live/real-time and that the return set contains flight-only offers rather than packages; it does not discuss rate limits or result volume, but an output schema exists to cover return shape.

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, front-loaded with what the tool is and the source, then usage triggers, then the negative case and the sibling routing. No filler and nothing repeated from the schema.

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?

With 17 optional parameters, an output schema and full annotation coverage, the description supplies the essential disambiguation and the real-time/flight-only framing. It could go further by noting that at least a destination or date is typically needed for useful results, which is the one remaining gap.

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 coverage is 100% with per-field descriptions, ranges and formats, so the schema does the heavy lifting for all 17 parameters. The description adds no parameter-level meaning (e.g. nothing about how the date-range params interact with exact dates), so 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 and resource ('Søg i realtid efter charterflytilbud (kun fly)') plus the source domain afbudsrejser.dk. It explicitly contrasts its output with package holidays, so an agent can distinguish it from search_holidays 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', 'flysæde', 'charterfly uden hotel', 'flybilletter') and explicitly routes the combined flight+hotel case to search_holidays. Both the when-to-use and the alternative are named.

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

Søg efter tilgængelige pakkerejser inklusive fly og overnatning med afrejse fra Danmark. Returnerer aktuelle priser, tilgængelighed, hoteloplysninger og bookinglinks, der matcher brugerens søgekriterier. Find tilgængelige pakkerejser fra Danmark baseret på søgekriterier.

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

Name	Required	Description
`results`	No