Gondola Award Travel Search

predict_price

Read-only

Predict whether the current rate at a hotel is a good deal based on historical price trends. Use this when the user is debating booking now vs. waiting. Returns a confidence-scored label (e.g. "book now", "wait", "prices typically rise") with supporting signals and price history.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hotel_id": "<hotel_id>",
      "checkin": "<checkin>",
      "checkout": "<checkout>",
      "nightly_cash_cost": "<nightly_cash_cost>",
      "nightly_cash_cost_currency": "<nightly_cash_cost_currency>"
    },
    "name": "predict_price"
  }
}

Input Schema

Name	Required	Description
`checkin`	Yes	Check-in date in YYYY-MM-DD format.
`checkout`	Yes	Check-out date in YYYY-MM-DD format.
`hotel_id`	Yes	The hotel's Vervotech property ID.
`nightly_cash_cost`	Yes	The current all-in nightly cash rate from search_hotels (stay total, including included taxes and fees, divided by nights).
`nightly_points_cost`	No	Optional current nightly points rate.
`nightly_cash_cost_currency`	Yes	Currency of the cash cost (e.g. "USD", "EUR").

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedInput schema / properties / nightly_cash_cost / description

Previous value: -"The current nightly cash rate to evaluate (from search_hotels)."New value: +"The current all-in nightly cash rate from search_hotels (stay total, including included taxes and fees, divided by nights)."

Changed1 schema field changedAug 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "predict_priceOutput",
+  "type": "object"
+}

Changed17 schema fields changedAug 26, 2026

addedInput schema / properties / checkin / description

Added value: +"Check-in date in YYYY-MM-DD format."

removedInput schema / properties / checkin / title
```
Removed value: -"Checkin"
```

addedInput schema / properties / checkout / description

Added value: +"Check-out date in YYYY-MM-DD format."

removedInput schema / properties / checkout / title
```
Removed value: -"Checkout"
```
addedInput schema / properties / hotel_id / description
```
Added value: +"The hotel's Vervotech property ID."
```
removedInput schema / properties / hotel_id / title
```
Removed value: -"Hotel Id"
```

addedInput schema / properties / nightly_cash_cost / description

Added value: +"The current nightly cash rate to evaluate (from search_hotels)."

removedInput schema / properties / nightly_cash_cost / title
```
Removed value: -"Nightly Cash Cost"
```
addedInput schema / properties / nightly_cash_cost_currency / description
```
Added value: +"Currency of the cash cost (e.g. \"USD\", \"EUR\")."
```
removedInput schema / properties / nightly_cash_cost_currency / title
```
Removed value: -"Nightly Cash Cost Currency"
```

removedInput schema / properties / nightly_points_cost / anyOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / nightly_points_cost / default
```
Removed value: -null
```
addedInput schema / properties / nightly_points_cost / description
```
Added value: +"Optional current nightly points rate."
```
removedInput schema / properties / nightly_points_cost / title
```
Removed value: -"Nightly Points Cost"
```
addedInput schema / properties / nightly_points_cost / type
```
Added value: +"integer"
```

removedInput schema / title

Removed value: -"predict_priceArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "predict_priceOutput",
-  "type": "object"
-}New value: +null

First observedJun 18, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=false, covering the safety profile. The description adds that it relies on historical price trends and returns a confidence-scored label with supporting signals and price history, but since an output schema exists, the return details are largely redundant and no extra behavioral context (e.g., auth, rate limits) is provided.

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?

Three sentences that are front-loaded and waste-free: purpose, usage context, return summary. Every sentence earns its place.

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 read-only prediction tool with full schema coverage, complete annotations, and an output schema, the description covers what it does, when to use it, and what it returns. It omits possible exclusions such as already-booked stays or points-only scenarios, leaving a minor gap.

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 the schema fully documents all six parameters, including required fields and the source of nightly_cash_cost. The description adds no parameter-level semantics beyond what is already in the schema, so the baseline 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?

States a specific verb 'Predict' and resource 'whether the current rate at a hotel is a good deal based on historical price trends', plus the output form (confidence-scored label). Although it doesn't name siblings, its predictive/advisory nature clearly distinguishes it from search, booking, and rate-listing tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Provides clear context: 'Use this when the user is debating booking now vs. waiting.' It does not name alternative tools or specify when not to use it, so it falls short of the explicit when/when-not/alternatives standard for a 5.

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

All Gondola Award 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.