Afbudsrejser travel search

Søg efter flytilbud fra Danmark

search_flights

Read-only

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.

Input Schema

TableJSON 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

TableJSON Schema

Name	Required	Description	Default
`total`	No
`offers`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "offers": {
+      "items": {
+        "properties": {
+          "offer_id": {
+            "type": "string"
+          },
+          "origin_destinations": {
+            "items": {
+              "properties": {
+                "arrival": {
+                  "properties": {
+                    "airport_code": {
+                      "type": "string"
+                    },
+                    "datetime": {
+                      "format": "date-time",
+                      "type": "string"
+                    }
+                  },
+                  "type": "object"
+                },
+                "departure": {
+                  "properties": {
+                    "airport_code": {
+                      "type": "string"
+                    },
+                    "datetime": {
+                      "format": "date-time",
+                      "type": "string"
+                    }
+                  },
+                  "type": "object"
+                },
+                "flight_numbers": {
+                  "items": {
+                    "type": "string"
+                  },
+                  "type": "array"
+                },
+                "stop_quantity": {
+                  "type": "integer"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "supplier": {
+            "type": "string"
+          },
+          "total_price": {
+            "properties": {
+              "amount": {
+                "type": "integer"
+              },
+              "currency_code": {
+                "type": "string"
+              },
+              "per_pax_amount": {
+                "type": "integer"
+              }
+            },
+            "type": "object"
+          },
+          "trip_duration_nights": {
+            "description": "Antal nætter (vendor extension, ikke standard NDC)",
+            "type": "integer"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedJul 16, 2026

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.

All Afbudsrejser travel search tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?