Afbudsrejser travel search
Server Details
Realtime package holiday and charter flight prices from Denmark. Inventory not on Google Flights.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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.
Tool Definition Quality
Average 3.2/5 across 2 of 2 tools scored.
The two tools have clearly distinct purposes: one searches for flights only, the other for package holidays. The descriptions explicitly differentiate them, leaving no ambiguity for an agent.
Both tools follow the same 'search_' prefix naming pattern, with the resource ('flights' or 'holidays') clearly indicating the target. This is perfectly consistent.
With only 2 tools, the server is lean but covers the two main travel search categories (flights and package holidays) for its Danish market focus. A few more tools (e.g., search_hotels) might be expected, but the count is reasonable for the niche.
The tool set covers the core travel search needs (flights and package holidays) for the Danish market. Minor gaps like standalone hotel or activity searches exist, but the primary offerings are present and agents can work around missing features.
Available Tools
2 toolssearch_flightsSøg efter flytilbud fra DanmarkAInspect
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.
| 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) |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions 'NDC-justeret API' and that data includes charter seats, but does not disclose whether the operation is read-only, authentication requirements, rate limits, or response format. The description lacks behavioral context beyond the basic purpose.
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, front-loading the core purpose in the first sentence, adding a unique value proposition in the second, and a summary call-to-action in the third. Every sentence provides distinct value with no redundancy.
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 high complexity (17 parameters, no output schema, no annotations), the description is insufficient. It does not explain how to use the various date parameters (exact vs range), the output format (list of offers), pagination, or sorting behavior beyond the parameter enum. The description leaves significant gaps for an agent to correctly invoke the tool.
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?
Schema description coverage is 100%, so the schema already documents all 17 parameters. The tool description does not add any additional meaning or context beyond what the parameter descriptions provide. Baseline 3 is appropriate.
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 flight-only deals from Denmark, specifically charter flights not found on major platforms. It uses a specific verb ('søge efter') and resource ('flyrejser') and distinguishes from the sibling 'search_holidays' by emphasizing 'kun fly' (only 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 implies when to use this tool: for flight-only searches from Denmark, especially for charter seats. It highlights unique data not available on other sites. However, it does not explicitly state when not to use it (e.g., for package holidays) or name the alternative tool 'search_holidays'.
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 DanmarkBInspect
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.
| 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 |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and description lacks behavioral details like rate limits, data freshness, or how results are aggregated. Only states it searches a database.
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?
Two sentences, efficient, though the list of providers could be shortened. Front-loaded with purpose.
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?
For a tool with 37 parameters and no output schema, description lacks context on return format, pagination, or result interpretation. Minimalist.
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?
Schema coverage is 100%, so baseline 3. Description adds no additional parameter meaning beyond what the schema already provides.
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 it's an API for searching package holiday offers in Denmark, listing major providers. It distinguishes from sibling 'search_flights' by focusing on package holidays.
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?
No guidance on when to use this tool versus alternatives. No mention of 'search_flights' or when to avoid this tool.
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.
Discussions
No comments yet. Be the first to start the discussion!