Realtime package holiday and charter flight prices from Denmark. Inventory not on Google Flights.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 3.8/5 across 2 of 2 tools scored.
The two tools target clearly distinct domains: flights vs. package holidays. There is no overlap in purpose, so an agent can easily select the right tool based on the search intent.
Both tools follow the exact same verb_noun pattern: search_ + resource. The naming is perfectly consistent and predictable.
With only two tools, the server feels slightly thin. While the two tools cover the core travel search categories, the count is on the low end of what would be expected for a travel search service.
The server covers the two primary travel products: flights and package holidays. It lacks search for hotels or standalone accommodation, but for a package-holiday-focused Danish travel search, the coverage is reasonably complete.
search_flightsSøg efter flytilbud fra DanmarkAInspectNDC-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.
| 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) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility for behavioral disclosure. It describes the tool as a search API (read-only implied) and notes it contains charter seats. However, it fails to mention any required authentication, rate limits, response format, or potential side effects, leaving behavioral traits underspecified.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences, front-loading the key differentiators (NDC, charter, Denmark-only) and unique value. No unnecessary words or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (17 parameters, no output schema, no annotations), the description adequately outlines the general purpose and data source. However, it lacks guidance on how parameters interact (e.g., exact dates vs. ranges) and what the output contains, which a complete description should address for effective tool selection and invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers all 17 parameters with descriptions (100% coverage), so the description adds no additional parameter-level semantics. Per criteria, baseline is 3. The description does not clarify relationships between parameters or provide usage examples beyond what the schema already offers.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool searches for flight-only offers from Denmark, specifically charter seats not found in other platforms. This distinguishes it from the sibling tool 'search_holidays' (holiday packages) and provides a specific verb-resource pair.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description indicates the ideal use case (flight-only charter searches from Denmark) and highlights unique selling points (NDC-adjusted, not in Google Flights etc.). It implies use when seeking charter flights, but does not explicitly state when not to use or mention alternative tools by name.
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 DanmarkAInspectAPI 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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that the tool searches a large database and aggregates offers from multiple suppliers, but it does not explicitly state that it is read-only, describe the response format, or mention any limitations. For a search tool, this is acceptable but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences and front-loaded with the main purpose. It contains some redundancy, such as 'API'et bruges til at give de bedste tilbud' which repeats the search concept, but it is still compact and free of irrelevant details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 37 parameters, no output schema, and no annotations, the description is minimal. It covers the high-level purpose and supplier scope but does not explain what the returned data looks like or how the many search criteria interact. The rich schema provides parameter details, but the overall picture is incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All 37 parameters have detailed descriptions in the schema, including formats, examples, and defaults. The description adds no additional parameter semantics, so the baseline score of 3 applies due to high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches for package holidays (pakkerejser) in Denmark through a large database, specifying it covers major tour operators like Spies, TUI, and Apollo. The title 'Søg efter afbudsrejser og pakkerejser fra Danmark' further clarifies the scope, and the resource is distinct from the sibling search_flights.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context: this is for finding package holidays from Denmark based on search criteria. However, it does not explicitly mention when not to use it or explicitly differentiate from search_flights, relying on the inherent subject distinction (holidays vs flights).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!