viajante

Overview Schema Source Related Servers Discussions Admin

Cheapest-dates calendar

search_dates

Read-onlyIdempotent

Compare day-by-day flight prices for one route over up to 31 days with origin-destination and ISO start/end dates. Use it to pick lower-cost travel dates.

Instructions

Cheapest-per-day calendar for one named route, up to 31 days. route is ORIGIN-DEST; start and end are ISO dates. Use search_flex for +/-N around one date. This calendar is HTTP only and has no fetch mode. If it returns blocked, stop: do not switch to a browser or follow with search_flex or search_flights. Currency and country as in search_flights. Viajante does not convert.

    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
`end`	Yes
`via`	No
`bags`	No
`sort`	No
`trip`	No	one-way
`cabin`	No	economy
`proxy`	No
`route`	Yes
`start`	Yes
`adults`	No
`nearby`	No
`nights`	No
`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
`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.

Changed39 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"
```

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 / end / title
```
Removed value: -"End"
```
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_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 / nearby / title
```
Removed value: -"Nearby"
```
removedInput schema / properties / nights / title
```
Removed value: -"Nights"
```
removedInput schema / properties / no_overnight / title
```
Removed value: -"No Overnight"
```
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 / route / title
```
Removed value: -"Route"
```
removedInput schema / properties / sort / title
```
Removed value: -"Sort"
```
removedInput schema / properties / start / title
```
Removed value: -"Start"
```
removedInput schema / properties / trip / title
```
Removed value: -"Trip"
```
removedInput schema / properties / via / title
```
Removed value: -"Via"
```
removedInput schema / title
```
Removed value: -"search_datesArguments"
```

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

A4.1/5.0

Behavior4/5

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

Adds real context beyond the annotations: HTTP-only transport, no fetch/browser fallback, blocking behavior, and the deadline_seconds failure mode where unfinished queries return error code deadline rather than empty results. Currency conversion behavior ('Viajante does not convert') is also disclosed. It stops short of saying anything about result shape, though the output schema covers that.

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?

Front-loaded with the core capability and scope before the alternatives and caveats; almost every sentence carries operational information. Minor drag from the oddly indented deadline_seconds block, but no filler.

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

Completeness3/5

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

The decision-critical behaviors (blocking, no fallback, deadline semantics) are covered and an output schema exists so return values need not be described. However, for a tool with 37 parameters and no schema documentation, an agent is still guessing on most optional filters, which is a meaningful completeness gap.

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?

With 37 parameters at 0% schema description coverage, the description carries the full burden, yet it explains only route, start, end, currency, country, and deadline_seconds. The remaining ~30 (sort, trip, cabin, adults, children, nearby, nights, price_cap, max_stops, airline/alliance filters, layover bounds, etc.) are left entirely undefined in both schema and description.

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: 'Cheapest-per-day calendar for one named route, up to 31 days', and pins the scope with route/start/end semantics. It explicitly contrasts itself with search_flex, so an agent can route between 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit alternative routing ('Use search_flex for +/-N around one date') and an explicit stop rule: on 'blocked', do not switch to browser or follow with search_flex or search_flights. Both when-to-use and when-not-to-use are stated.

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