Restplass travel search

Søk etter flytilbud fra Norge

search_flights

Read-only

NDC-justert API for å søke etter flyreiser (kun fly) tilgjengelig fra Norge. Databasen inneholder seter på charterfly som vanligvis ikke finnes hos Google Flights, Skyscanner eller Kayak. Finn de beste tilgjengelige flytilbudene basert på søkekriterier.

Input Schema

TableJSON 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

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": "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

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds context about NDC alignment and the unique charter inventory, which is useful but not behavioral in the sense of side effects or response handling. It does not describe output structure or pagination, but given the output schema exists and annotations cover the safety profile, this is acceptable.

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?

The description is three sentences, each carrying relevant information: the core purpose, the unique value proposition (charter inventory), and the result orientation. It is front-loaded with the most important details and contains no filler or repetition.

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?

Given the tool has 17 parameters but 100% schema coverage, an output schema, and annotations covering safety, the description provides adequate context. It clarifies the geographical scope (from Norway) and the niche (charter seats), which are not in the schema. It does not explain when to use date ranges vs exact dates, but that is implicitly in the schema. Overall, it is complete enough for an agent to invoke correctly.

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%, meaning every parameter is already documented in the input schema. The description only generically mentions 'søkekriterier' (search criteria) without adding specific parameter semantics beyond what the schema provides. Since the schema fully covers parameters, the baseline of 3 is appropriate.

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?

The description clearly states the tool's purpose: to search for flight offers (flights only) available from Norway. The verb 'søke' (search) is specific, and the resource is well-defined. It explicitly differentiates from the sibling 'search_holidays' by emphasizing 'kun fly' (flights only), so an agent can distinguish them without opening the schema.

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 usage context by noting it covers charter flights not found on major booking sites and is limited to flights from Norway. However, it does not explicitly mention when to use this tool versus the sibling 'search_holidays' or when not to use it. The guidance is implied rather than explicit, so it earns a mid-range score.

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?