Skip to main content
Glama

Gondola Award Travel Search

by ai.gondola
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checkinYesCheck-in date in YYYY-MM-DD format.
checkoutYesCheck-out date in YYYY-MM-DD format.
hotel_idYesThe hotel's Vervotech property ID.
nightly_cash_costYesThe current all-in nightly cash rate from search_hotels (stay total, including included taxes and fees, divided by nights).
nightly_points_costNoOptional current nightly points rate.
nightly_cash_cost_currencyYesCurrency of the cash cost (e.g. "USD", "EUR").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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)."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "predict_priceOutput",
+  "type": "object"
+}
  3. Changed17 schema fields changed
    • 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
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds meaningful behavioral context by stating that it returns a confidence-scored label with supporting signals and price history, and that the prediction is based on historical trends rather than a guarantee.

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 earning its place: what the tool does, when to use it, and what it returns. It is front-loaded with the core purpose and contains no filler or redundant restatement.

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?

The description, combined with full schema coverage, an output schema, and safety annotations, provides enough context for an agent to select and invoke the tool correctly. It could be slightly stronger by naming related alternatives or noting limitations, but nothing essential for basic invocation is missing.

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 input schema fully documents all parameters and their meaning. The description does not add parameter-level detail beyond the schema, which matches the baseline of 3.

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 clearly states the tool's function: predicting whether a current hotel rate is a good deal based on historical price trends. It is specific about the verb and resource, and the use-case framing helps separate it from generic rate lookup tools, though it does not explicitly name or contrast sibling 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?

The description gives an explicit when-to-use condition: when the user is debating booking now versus waiting. This is clear and actionable, but it does not provide exclusions or alternatives such as when to use diagnose_rates or compare_rates instead.

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 toolsInspect
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