PriceWin

Poll Search Results

poll_search_results

Read-only

Returns the current results of a hotel search session started by search_hotels_live: hotels with their price from each source, and OpenTravel direct listings with the propertyId that get_hotel_detail and get_hotel_info take. Results can be partial while the search runs; status reads 'completed' once every source has answered.

Input Schema

Name	Required	Description
`area`	No	Optional override for the area filter captured at search time
`limit`	No	Max hotels to return; 0 = all (default 50)
`nights`	Yes	Number of nights
`offset`	No	Skip first N hotels for pagination (default 0)
`priceMax`	No	Optional override for the maximum-price filter
`priceMin`	No	Optional override for the minimum-price filter
`hotelName`	No	Optional override for the hotel-name filter captured at search time
`sessionId`	Yes	Session ID from search_hotels_live
`priceCurrency`	No	ISO 4217 code of priceMin/priceMax; defaults to the UI language's currency

Output Schema

Name	Required	Description	Default
`city`	Yes
`tier`	Yes
`limit`	Yes
`cached`	No
`hotels`	Yes
`nights`	Yes
`offset`	Yes
`status`	Yes
`checkIn`	Yes
`fxRates`	Yes
`hasMore`	Yes
`checkOut`	Yes
`language`	No
`progress`	Yes
`sessionId`	No
`agodaStatus`	Yes
`totalHotels`	Yes
`bookingStatus`	Yes
`longStayNotice`	No
`travelokaStatus`	Yes
`opentravelStatus`	Yes
`tier2AgodaStatus`	Yes
`opentravelResults`	Yes
`tier2BookingStatus`	Yes
`tier2TravelokaStatus`	Yes
`opentravelIndicativeResults`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026
- addedOutput schema / properties / hotels / items / properties / prices / properties / airbnb
```
Added value: +{
+  "$ref": "#/properties/hotels/items/properties/prices/properties/agoda"
+}
```
Changed5 schema fields changedOct 12, 2026
- addedOutput schema / properties / hotels / items / properties / prices / properties / expedia
```
Added value: +{
+  "$ref": "#/properties/hotels/items/properties/prices/properties/agoda"
+}
```
- addedOutput schema / properties / hotels / items / properties / prices / properties / hotelscom
```
Added value: +{
+  "$ref": "#/properties/hotels/items/properties/prices/properties/agoda"
+}
```
- addedOutput schema / properties / hotels / items / properties / prices / properties / official
```
Added value: +{
+  "$ref": "#/properties/hotels/items/properties/prices/properties/agoda"
+}
```
- addedOutput schema / properties / hotels / items / properties / prices / properties / priceline
```
Added value: +{
+  "$ref": "#/properties/hotels/items/properties/prices/properties/agoda"
+}
```
- addedOutput schema / properties / hotels / items / properties / prices / properties / tripcom
```
Added value: +{
+  "$ref": "#/properties/hotels/items/properties/prices/properties/agoda"
+}
```
Changed3 schema fields changedOct 6, 2026
- removedInput schema / properties / sessionId / maxLength
```
Removed value: -128
```
- removedInput schema / properties / sessionId / minLength
```
Removed value: -1
```
- addedInput schema / properties / sessionId / pattern
```
Added value: +"^[A-Za-z0-9_-]{1,64}(\\.[A-Za-z0-9_-]{1,16})?$"
```
First observedOct 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description adds genuine behavioral value beyond that: results can be partial while the search runs, and status flips to 'completed' only once every source has answered. It also flags that OpenTravel listings carry a propertyId consumable by get_hotel_detail/get_hotel_info.

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?

Two sentences, front-loaded with purpose and then the polling/completion semantics, with zero wasted wording. Every clause carries information an agent needs.

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?

An output schema exists, so return-value detail is not required, yet the description still sketches the payload (hotels with per-source prices, OpenTravel listings with propertyId). Combined with the partial-results behavior, it covers what an agent needs to poll and chain into detail tools correctly.

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 every parameter including the optional override filters is already documented in the schema. The description adds no parameter-level detail beyond what the schema provides, making the baseline 3 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 and resource ('Returns the current results of a hotel search session') and anchors it to the originating tool, search_hotels_live. This lets an agent distinguish it from search_hotels_live (which starts a search) and from the sibling poll_flight_results without opening either schema.

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?

It clearly establishes the calling context (a session started by search_hotels_live) and tells the agent how to know when to stop polling via the 'completed' status. It stops short of naming explicit when-not conditions, but the usage is unambiguous.

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

All PriceWin 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.

Resources

Need Help?