Gondola Award Travel Search

get_hotel_stats

Read-only

Get pricing percentile context for a specific hotel. Returns where the current rate falls relative to the property's typical pricing (e.g. "this rate is in the 20th percentile — cheaper than 80% of historical observations"). Use this to add objective context to recommendations.

Input Schema

TableJSON Schema

Name	Required	Description
`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 to additionally score.
`nightly_cash_cost_currency`	Yes	Currency of the cash cost (e.g. "USD").

Output Schema

TableJSON 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 score."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": "get_hotel_statsOutput",
+  "type": "object"
+}

Changed13 schema fields changedAug 26, 2026

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 score."
```
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\")."
```
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 to additionally score."

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: -"get_hotel_statsArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_hotel_statsOutput",
-  "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 and destructiveHint=false, so safety is covered. The description adds useful context about historical observations and percentile interpretation, but does not disclose potential limitations such as insufficient data or behavior when no history is available.

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, no filler, with the core function front-loaded and a helpful clarifying example. 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?

The description, combined with the full parameter schema and output schema, gives an agent enough to call the tool correctly. It clearly states purpose and output semantics, though it could briefly mention the optional nightly_points_cost behavior or data availability caveats.

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 parameters. The description does not add explicit parameter-level meaning beyond referring to the 'current rate,' which maps to nightly_cash_cost. Baseline 3 applies because the schema handles the heavy lifting.

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?

The description clearly specifies the verb 'Get' and the unique resource 'pricing percentile context for a specific hotel.' It immediately distinguishes this tool from siblings like predict_price, compare_rates, and diagnose_rates by focusing on percentile context relative to historical property pricing.

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 provides a clear usage context: 'Use this to add objective context to recommendations.' It does not explicitly mention alternatives or when not to use it, but the intended scenario is stated well enough for an agent to decide.

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.