viajante

Overview Schema Source Related Servers Discussions Admin

Search hotels

search_hotels

Read-onlyIdempotent

Search hotels by location and dates to compare total-stay prices in your chosen currency, with filters for rating, distance, entire homes, and free cancellation.

Instructions

Hotel search. Quotes are total-stay prices, not per person. Currency is required (no origin airport), except source skiplagged, whose quotes are USD. Quotes come back in the requested currency as the provider returned them. Viajante does not convert and never invents ISO 4217. location is one named place: ask when it is a typo, a region, or several candidate towns. The request carries adults and rooms only; do not state a room split. Google offers are in price order, not advice: weigh location, latitude and longitude, and review_count yourself. stays batches up to 8 location/check_in/check_out objects in one call. property_matrix lists each property's total per stay, null where it was not returned (not proof of unavailability), sorted by name. near is a point you name, {lat, lng}; max_distance_km needs it. entire_home=true asks for a house or villa; those offers carry sleeps, bedrooms and beds. lodging_evidence_conflict marks contradictory room or unit labels. Full rules: get_guide.

    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
`near`	No
`rooms`	No
`stays`	No
`adults`	No
`source`	No	google
`check_in`	No
`currency`	No
`location`	No
`check_out`	No
`min_rating`	No
`entire_home`	No
`max_distance_km`	No
`deadline_seconds`	No
`free_cancellation`	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.

Changed17 schema fields changedv1.5.2Oct 19, 2026

removedInput schema / properties / adults / title
```
Removed value: -"Adults"
```
removedInput schema / properties / check_in / title
```
Removed value: -"Check In"
```
removedInput schema / properties / check_out / title
```
Removed value: -"Check Out"
```
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 / entire_home / title
```
Removed value: -"Entire Home"
```
removedInput schema / properties / free_cancellation / title
```
Removed value: -"Free Cancellation"
```
removedInput schema / properties / location / title
```
Removed value: -"Location"
```
removedInput schema / properties / max_distance_km / title
```
Removed value: -"Max Distance Km"
```
removedInput schema / properties / min_rating / title
```
Removed value: -"Min Rating"
```
removedInput schema / properties / near / title
```
Removed value: -"Near"
```
removedInput schema / properties / rooms / title
```
Removed value: -"Rooms"
```
removedInput schema / properties / source / title
```
Removed value: -"Source"
```
removedInput schema / properties / stays / title
```
Removed value: -"Stays"
```
removedInput schema / properties / top / title
```
Removed value: -"Top"
```

removedInput schema / title

Removed value: -"search_hotelsArguments"

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"
+}

Changed13 schema fields changedv1.4.1Oct 6, 2026

addedInput schema / properties / check_in / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / check_in / default
```
Added value: +null
```
removedInput schema / properties / check_in / type
```
Removed value: -"string"
```

addedInput schema / properties / check_out / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / check_out / default
```
Added value: +null
```
removedInput schema / properties / check_out / type
```
Removed value: -"string"
```

addedInput schema / properties / location / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / location / default
```
Added value: +null
```
removedInput schema / properties / location / type
```
Removed value: -"string"
```

addedInput schema / properties / max_distance_km

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Max Distance Km"
+}

addedInput schema / properties / near

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "type": "number"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Near"
+}

addedInput schema / properties / stays

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Stays"
+}

removedInput schema / required

Removed value: -[
-  "location",
-  "check_in",
-  "check_out"
-]

First observedv1.0.0Sep 9, 2026

TDQS

A3.8/5.0

Behavior5/5

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

Annotations already cover read-only, open-world, idempotent and non-destructive, and the description still adds substantial behavioral context beyond them: no currency conversion and no invented ISO codes, deadline_seconds yields error code 'deadline' (not loaded, not empty), property_matrix nulls are not proof of unavailability, and Google ordering is not advice. These are exactly the non-obvious traits an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Nearly every sentence carries real information, so it is not padded, but it is delivered as a dense telegraphic wall that mixes input-parameter semantics with output-field semantics (property_matrix, lodging_evidence_conflict) and ends with an oddly indented deadline_seconds note. It is hard to scan and not cleanly front-loaded.

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?

An output schema exists so return shape needn't be explained, and the description covers most behavior for a 15-parameter tool. However, with zero schema descriptions it leaves min_rating, free_cancellation, and top entirely undocumented, and never clarifies that all parameters are optional or which combination of location/check_in/check_out is actually required to get a useful result.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the load, and it does for most high-stakes parameters: currency and the skiplagged USD exception, location as a single named place, adults/rooms with no room split, stays batching up to 8 objects, near as {lat,lng} with max_distance_km depending on it, entire_home semantics, and deadline_seconds. It stops short of documenting top, min_rating, and free_cancellation, so coverage of the 15 parameters is strong but incomplete.

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 description opens with a specific verb+resource ('Hotel search') and immediately scopes it with substantive semantics (total-stay quotes, currency behavior, batch mode via stays). It differentiates the scope of the search from the downstream artifacts it produces (property_matrix, lodging_evidence_conflict), though it never explicitly contrasts itself with close siblings like search_hotel_rooms or get_hotel_details.

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?

Usage is implied rather than stated: it says to ask when 'location' is a typo/region/multiple towns, forbids stating a room split, and routes to get_guide for 'full rules'. But there is no explicit when-to-use-this-instead-of-X guidance against a 22-tool sibling set, which leaves the routing burden on the agent.

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