viajante

Overview Schema Source Related Servers Discussions Admin

Explore destinations

search_explore

Read-onlyIdempotent

Explore destinations from one origin to get a priced shortlist of flights; use it to compare where to fly next based on dates, budget, cabin, and stops.

Instructions

Destinations from one origin, then a priced shortlist. Give start (ISO date) or month, not both. Needs the browser extra; one adult in economy only. Currency and country as in search_flights. Viajante does not convert. A destination without a price is not_loaded, not a usable row.

    deadline_seconds stops starting queries after that many seconds; unfinished
    queries are error code deadline (not loaded, not empty). See get_guide.

Input Schema

TableJSON Schema

Name	Required	Default
`top`	No
`via`	No
`bags`	No
`days`	No
`sort`	No	price
`cabin`	No	economy
`month`	No
`proxy`	No
`start`	No
`adults`	No
`nearby`	No
`origin`	Yes
`country`	No
`airlines`	No
`alliance`	No
`carry_on`	No
`children`	No
`currency`	No
`max_stops`	No
`price_cap`	No
`exclude_via`	No
`max_layover`	No
`min_layover`	No
`depart_after`	No
`max_duration`	No
`no_overnight`	No
`arrive_before`	No
`depart_window`	No
`baggage_buffer`	No
`infants_on_lap`	No
`exclude_regions`	No
`infants_in_seat`	No
`deadline_seconds`	No
`exclude_airlines`	No
`exclude_airports`	No
`exclude_alliance`	No
`include_airports`	No
`require_overnight`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`empty_note`	Yes
`error_code`	Yes
`observed_at`	Yes
`retry_after`	Yes
`completeness`	Yes
`empty_reason`	Yes
`observed_at_basis`	Yes
`retry_after_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed40 schema fields changedv1.5.2Oct 19, 2026

removedInput schema / properties / adults / title
```
Removed value: -"Adults"
```
removedInput schema / properties / airlines / title
```
Removed value: -"Airlines"
```
removedInput schema / properties / alliance / title
```
Removed value: -"Alliance"
```
removedInput schema / properties / arrive_before / title
```
Removed value: -"Arrive Before"
```
removedInput schema / properties / baggage_buffer / title
```
Removed value: -"Baggage Buffer"
```
removedInput schema / properties / bags / title
```
Removed value: -"Bags"
```
removedInput schema / properties / cabin / title
```
Removed value: -"Cabin"
```
removedInput schema / properties / carry_on / title
```
Removed value: -"Carry On"
```
removedInput schema / properties / children / title
```
Removed value: -"Children"
```
removedInput schema / properties / country / title
```
Removed value: -"Country"
```
removedInput schema / properties / currency / title
```
Removed value: -"Currency"
```
removedInput schema / properties / days / title
```
Removed value: -"Days"
```

addedInput schema / properties / deadline_seconds

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

removedInput schema / properties / depart_after / title
```
Removed value: -"Depart After"
```
removedInput schema / properties / depart_window / title
```
Removed value: -"Depart Window"
```
removedInput schema / properties / exclude_airlines / title
```
Removed value: -"Exclude Airlines"
```
removedInput schema / properties / exclude_airports / title
```
Removed value: -"Exclude Airports"
```
removedInput schema / properties / exclude_alliance / title
```
Removed value: -"Exclude Alliance"
```
removedInput schema / properties / exclude_regions / title
```
Removed value: -"Exclude Regions"
```
removedInput schema / properties / exclude_via / title
```
Removed value: -"Exclude Via"
```
removedInput schema / properties / include_airports / title
```
Removed value: -"Include Airports"
```
removedInput schema / properties / infants_in_seat / title
```
Removed value: -"Infants In Seat"
```
removedInput schema / properties / infants_on_lap / title
```
Removed value: -"Infants On Lap"
```
removedInput schema / properties / max_duration / title
```
Removed value: -"Max Duration"
```
removedInput schema / properties / max_layover / title
```
Removed value: -"Max Layover"
```
removedInput schema / properties / max_stops / title
```
Removed value: -"Max Stops"
```
removedInput schema / properties / min_layover / title
```
Removed value: -"Min Layover"
```
removedInput schema / properties / month / title
```
Removed value: -"Month"
```
removedInput schema / properties / nearby / title
```
Removed value: -"Nearby"
```
removedInput schema / properties / no_overnight / title
```
Removed value: -"No Overnight"
```
removedInput schema / properties / origin / title
```
Removed value: -"Origin"
```
removedInput schema / properties / price_cap / title
```
Removed value: -"Price Cap"
```
removedInput schema / properties / proxy / title
```
Removed value: -"Proxy"
```
removedInput schema / properties / require_overnight / title
```
Removed value: -"Require Overnight"
```
removedInput schema / properties / sort / title
```
Removed value: -"Sort"
```
removedInput schema / properties / start / title
```
Removed value: -"Start"
```
removedInput schema / properties / top / title
```
Removed value: -"Top"
```
removedInput schema / properties / via / title
```
Removed value: -"Via"
```

removedInput schema / title

Removed value: -"search_exploreArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "completeness": {
+      "enum": [
+        "complete",
+        "partial",
+        "blocked"
+      ],
+      "type": "string"
+    },
+    "empty_note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "empty_reason": {
+      "anyOf": [
+        {
+          "enum": [
+            "provider_empty",
+            "filtered_out",
+            "not_loaded"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "error_code": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "observed_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "observed_at_basis": {
+      "anyOf": [
+        {
+          "enum": [
+            "provider",
+            "fetch"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "retry_after": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "retry_after_seconds": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "status": {
+      "enum": [
+        "ok",
+        "no_results",
+        "rate_limited",
+        "blocked",
+        "timeout",
+        "failed"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "completeness",
+    "empty_reason",
+    "empty_note",
+    "error_code",
+    "retry_after",
+    "retry_after_seconds",
+    "observed_at",
+    "observed_at_basis"
+  ],
+  "type": "object"
+}

First observedv1.0.0Sep 9, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Beyond the annotations (which already cover read-only, idempotent, non-destructive, open-world), the description adds real behavioral detail: a dependency requirement ('browser extra'), no currency conversion, unpriced destinations surfacing as not_loaded, and timeout semantics via deadline_seconds returning error code deadline rather than an empty result.

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?

The purpose is front-loaded and the text is dense but short for a 38-parameter tool; each sentence carries information. The stray indentation in the second paragraph and heavy reliance on cross-references ('as in search_flights', 'See get_guide') slightly hurt readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 38-parameter exploration tool with zero schema description coverage, the description leaves most inputs unexplained, which is a substantial gap even though an output schema exists and the safety profile is covered by annotations. The error/prerequisite notes are good but do not compensate for the parameter coverage void.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 38 parameters, so the description carries the full burden, yet it meaningfully covers only a handful (start, month, currency, country, deadline_seconds, and the adults/cabin restrictions). The other ~30 parameters (top, via, bags, sort, price_cap, max_layover, exclude_*, require_overnight, etc.) are undefined in both schema and description.

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 opening sentence names the resource and the two-stage output ('Destinations from one origin, then a priced shortlist'), so an agent knows it returns priced destination options from a single origin. It does not, however, differentiate itself from plausible siblings like search_dates or search_flex, so the agent must infer the boundary.

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?

It gives hard operating constraints ('Needs the browser extra', 'one adult in economy only') and an input rule ('Give start ... or month, not both'), plus a pointer to get_guide. It never states when to prefer this tool over search_dates/search_flex/search_trip, so usage context is only implied.

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