upgrade-agent

Predict Bid Success

predict_bid_success

Read-onlyIdempotent

Estimates how likely a specific bid amount is to be accepted, grounded in resolved bid outcomes for the carrier cabin, plus the operator's own bid-strength read when a checked booking's session id is provided. Returns null when there isn't enough data.

Input Schema

TableJSON Schema

Name	Required	Description
`cabin`	No	Optional: target cabin.
`amount`	Yes	The bid amount to evaluate, in the operator's offer currency.
`carrier`	No	Operator IATA code or name, e.g. 'LH' or 'Lufthansa'. Optional if conversationId carries the operator from earlier.
`segment`	No	Route 'YUL-LHR' or flight number, if the booking has more than one bid-eligible segment.
`sessionId`	No	The sessionId from start_eligibility_check — unlocks the operator's LIVE bid-strength read for this exact booking and amount.
`conversationId`	No	Optional stable conversation id — reuses the operator (and checked booking) in play.
`travelerQuestion`	No	The traveler's request in their own words, verbatim (e.g. 'can I upgrade my Swiss flight to business?'). For privacy, leave out the booking reference, last name, email, and other personal details. Pass it whenever the traveler asked in free text — it improves the assistant's answers over time.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

changedInput schema / properties / travelerQuestion / description

Previous value: -"The traveler's request in their own words, verbatim (e.g. 'can I upgrade my Swiss flight to business?'). For privacy, leave out the booking reference, last name, email, and other personal details. Pass it whenever the traveler asked in free text — it improves Upgrade Agent's answers over time."New value: +"The traveler's request in their own words, verbatim (e.g. 'can I upgrade my Swiss flight to business?'). For privacy, leave out the booking reference, last name, email, and other personal details. Pass it whenever the traveler asked in free text — it improves the assistant's answers over time."

Changed1 schema field changedSep 22, 2026

changedOutput schema / (root)

Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "band": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "bidAnalysis": {
-      "anyOf": [
-        {
-          "additionalProperties": false,
-          "properties": {
-            "score": {
-              "type": [
-                "number",
-                "null"
-              ]
-            },
-            "strength": {
-              "type": "string"
-            },
-            "text": {
-              "type": [
-                "string",
-                "null"
-              ]
-            }
-          },
-          "required": [
-            "strength"
-          ],
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "The operator's own LIVE strength read for this amount on this booking (present when sessionId resolves to a checked booking)."
-    },
-    "confidence": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "note": {
-      "description": "Why no probability was returned (invalid input / unknown operator / insufficient resolved outcomes). Relay this honestly.",
-      "type": "string"
-    },
-    "probability": {
-      "description": "Estimated success probability (0–1), or null when there's too little resolved data.",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "samples": {
-      "description": "Number of resolved bids the estimate is based on.",
-      "type": [
-        "number",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed5 schema fields changedSep 22, 2026

changedInput schema / properties / conversationId / description

Previous value: -"Optional stable conversation id — reuses the operator in play."New value: +"Optional stable conversation id — reuses the operator (and checked booking) in play."

addedInput schema / properties / segment

Added value: +{
+  "description": "Route 'YUL-LHR' or flight number, if the booking has more than one bid-eligible segment.",
+  "type": "string"
+}

addedInput schema / properties / sessionId

Added value: +{
+  "description": "The sessionId from start_eligibility_check — unlocks the operator's LIVE bid-strength read for this exact booking and amount.",
+  "type": "string"
+}

changedInput schema / properties / travelerQuestion / description

Previous value: -"The traveler's request in their own words, verbatim (e.g. 'can I upgrade my Swiss flight to business?'). NEVER include the booking reference, last name, email, or other personal details. Pass it whenever the traveler asked in free text — it improves Upgrade Agent's answers over time."New value: +"The traveler's request in their own words, verbatim (e.g. 'can I upgrade my Swiss flight to business?'). For privacy, leave out the booking reference, last name, email, and other personal details. Pass it whenever the traveler asked in free text — it improves Upgrade Agent's answers over time."

addedOutput schema / properties / bidAnalysis

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "score": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "strength": {
+          "type": "string"
+        },
+        "text": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "strength"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The operator's own LIVE strength read for this amount on this booking (present when sessionId resolves to a checked booking)."
+}

Changed1 schema field changedJul 8, 2026

addedInput schema / properties / travelerQuestion

Added value: +{
+  "description": "The traveler's request in their own words, verbatim (e.g. 'can I upgrade my Swiss flight to business?'). NEVER include the booking reference, last name, email, or other personal details. Pass it whenever the traveler asked in free text — it improves Upgrade Agent's answers over time.",
+  "type": "string"
+}

Changed1 schema field changedJul 8, 2026

addedOutput schema / properties / note

Added value: +{
+  "description": "Why no probability was returned (invalid input / unknown operator / insufficient resolved outcomes). Relay this honestly.",
+  "type": "string"
+}

AddedJul 2, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish this is a safe, idempotent, non-destructive read, so the burden is lower. The description adds genuine behavioral context beyond them: it discloses the data sources (resolved bid outcomes, operator read), the sessionId dependency, and that null is returned when data is insufficient — a useful failure-mode disclosure.

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?

Two dense sentences that front-load the core purpose and then layer the data-grounding and null behavior. Every clause carries information, though the second sentence is packed tightly enough to require a second read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should describe the return shape, but it only says it returns null when data is short — not what a successful result looks like (probability, score, label, or confidence). It covers the input prerequisites well but leaves the output contract underspecified for a 7-parameter analytic tool.

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 coverage is 100%, so every parameter is already documented in the schema, including the sessionId provenance and the travelerQuestion privacy guidance. The description mostly reinforces this ('sessionId ... unlocks the operator's LIVE bid-strength read'), adding the causal link between live data and the sessionId but little syntax or format detail beyond the schema. 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+resource: estimating the acceptance likelihood of a given bid amount, grounded in resolved bid outcomes and the operator's bid-strength read. This clearly separates it from siblings like get_bid_status (status of an existing bid) or get_upgrade_pricing (price discovery), though it never names an alternative explicitly.

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?

Implies usage through the sessionId condition ('unlocks the LIVE bid-strength read for this exact booking and amount') and the null fallback, which hints at a data-availability prerequisite. But it never says when to prefer this over get_upgrade_pricing, get_bid_status, or check_upgrade_eligibility, leaving the routing decision to inference.

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

All upgrade-agent 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?