Restplass travel search

Søk etter flytilbud fra Norge

search_flights

Read-only

Søk i sanntid etter charterflytilbud (kun fly) fra restplass.no. Bruk ved forespørsler om fly uten overnatting, f.eks. 'kun fly', 'flysete', 'charterfly uten hotell' og 'flybilletter'. Returnerer tilgjengelige flytilbud, ikke pakkereiser. For fly og hotell, bruk search_holidays.

Input Schema

Name	Required	Description	Default
`adt`	No	Antall voksne (NDC: PaxType=ADT), default 1
`chd`	No	Antall barn (NDC: PaxType=CHD), default 0
`inf`	No	Antall spedbarn (NDC: PaxType=INF), default 0
`dest`	No	IATA kode for destinasjonsflyplass, f.eks. AYT, AGP, TFS
`orig`	No	IATA kode for avreiseflyplass, f.eks. OSL, SVG, TRD
`sort`	No	Sorteringsrekkefølge, default price_asc	price_asc
`limit`	No	Antall tilbud som returneres (1-25), default 10
`direct`	No	Kun direktefly (NDC: StopQuantity=0)
`dep_date`	No	Eksakt utreisedato (YYYY-MM-DD)
`ret_date`	No	Eksakt returdato (YYYY-MM-DD)
`max_price`	No	Maksimum totalpris (NDC: PriceRangeFilter.MaxAmount)
`nights_max`	No	Maksimum antall netter (vendor extension, ikke NDC)
`nights_min`	No	Minimum antall netter (vendor extension, ikke NDC)
`dep_date_to`	No	Seneste utreisedato (YYYY-MM-DD)
`ret_date_to`	No	Seneste returdato (YYYY-MM-DD)
`dep_date_from`	No	Tidligste utreisedato (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": "Antall netter (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.3/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 is covered. The description adds useful behavior beyond that: results are real-time, sourced from restplass.no, and contain flight offers rather than package holidays. It does not mention pagination, result volume behaviour, or rate limits, so it stops short of a 5.

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?

Four short, front-loaded sentences that put purpose and the flight-only constraint first, followed by the sibling alternative. Slight redundancy between "(kun fly)" and "Returnerer tilgjengelige flytilbud, ikke pakkereiser", which keeps it from a 5.

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 17-parameter, zero-required search tool with an output schema and rich annotations, the description covers purpose, scope, triggers, and the sibling boundary. What it omits (date-range vs exact-date interplay, sorting defaults) is already fully specified in the schema, so nothing critical 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%, so all 17 parameters, their defaults, ranges, and NDC mappings are already documented. The description adds no parameter guidance at all (e.g. it never clarifies when to use dep_date vs dep_date_from/to or how nights_* interacts with ret_date), so the 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 ("Søk"), resource ("charterflytilbud (kun fly)"), and source (restplass.no), plus scope restriction to flight-only. It explicitly contrasts with the sibling search_holidays, so an agent can distinguish the two 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", "flysete", "charterfly uten hotell", "flybilletter") and names the alternative for the flight+hotel case: "For fly og hotell, bruk search_holidays." Both when-to-use and when-to-use-something-else are covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Restplass 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?