Afbudsrejser travel search

Søg efter flytilbud fra Danmark

search_flights

Read-only

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.

Input 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

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

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.

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?