PriceWin

Poll Flight Results

poll_flight_results

Read-only

Returns the current results of a flight search session started by search_flights_live: outbound and return options with airline, flight number, times, stops, the cheapest fare and every site's fare with its booking link (offers). Results can be partial while the search runs; status reads 'completed' or 'failed' when it ends.

Input Schema

Name	Required	Description
`limit`	No	Maximum results per direction. Zero returns the full structured page for the widget.
`offset`	No	Starting result index per direction.
`sessionId`	Yes	Session ID from search_flights_live

Output Schema

Name	Required	Description	Default
`cabin`	Yes
`adults`	Yes
`cached`	Yes
`origin`	Yes
`status`	Yes
`language`	No
`tripType`	Yes
`sessionId`	Yes
`returnDate`	No
`destination`	Yes
`totalReturn`	Yes
`departureDate`	Yes
`returnFlights`	Yes
`totalOutbound`	Yes
`outboundFlights`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 15,
+  "description": "Maximum results per direction. Zero returns the full structured page for the widget.",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Starting result index per direction.",
+  "maximum": 10000,
+  "minimum": 0,
+  "type": "integer"
+}

Changed2 schema fields changedOct 25, 2026

addedOutput schema / properties / outboundFlights / items / properties / agent
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / outboundFlights / items / properties / offers

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "agent": {
+        "type": "string"
+      },
+      "agentCode": {
+        "type": "string"
+      },
+      "bookingUrl": {
+        "type": "string"
+      },
+      "currency": {
+        "type": "string"
+      },
+      "price": {
+        "type": "number"
+      },
+      "pricePerTraveler": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "agent",
+      "agentCode",
+      "price",
+      "pricePerTraveler",
+      "currency",
+      "bookingUrl"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

First observedOct 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description needn't restate safety. It adds real behavioral context beyond annotations: results can be partial mid-search, and status transitions to 'completed' or 'failed' when finished — the key trait for a polling tool. It doesn't mention rate limiting or how often polling is expected, a minor remaining gap.

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

Conciseness4/5

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

Front-loads the core purpose and the originating session, then layers in what's returned and the status lifecycle. Dense and mostly waste-free; the enumerated result fields (airline, flight number, times, stops, fares) are somewhat verbose given an output schema exists, slightly denting efficiency.

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?

Given an output schema exists, the description needn't describe return shape, yet it usefully summarizes what offers/status contain while covering the polling lifecycle. For a read-only tool with full schema and annotations, this is complete enough to invoke and interpret correctly; only polling cadence guidance 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 schema already documents limit, offset and sessionId with defaults and ranges. The description reinforces that sessionId comes from search_flights_live but adds no pagination or limit=0 widget behavior beyond what the schema states. Baseline 3 applies.

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?

States a specific verb ('Returns the current results') and resource (flight search session results), and ties itself to the sibling search_flights_live as the creator. It doesn't differentiate from the sibling poll_search_results (generic poller), leaving some ambiguity for an agent choosing between the two pollers.

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?

Prerequisite is clear ('session started by search_flights_live') and the partial-while-running plus completed/failed status strongly implies a poll-until-done loop. However, it never explicitly says to call repeatedly until status is terminal, nor does it steer the agent away from poll_search_results or state retry/cadence guidance.

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?