upgrade-agent

Check Booking Eligibility

check_upgrade_eligibility

Looks up a booking's upgrade eligibility from a booking reference and last name, and airline. Returns eligibility status, upgrade options, bid ranges, and a session id for follow-up bid tools.

Input Schema

TableJSON Schema

Name	Required	Description
`pnr`	Yes	The booking reference or PNR (e.g. ABC123).
`carrier`	No	Airline/cruise/rail name or IATA code (e.g. 'SWISS' or 'LX').
`language`	No	ISO 639-1 language for the offer page (e.g. 'fr', 'es'). Defaults to 'en'.
`lastName`	Yes	Passenger last name, exactly as it appears on the booking.
`intentContext`	No	The traveler's stated shopping intent — bound to the session and surfaced back so offers are presented against it.
`conversationId`	No	Optional stable conversation id — lets place_bid/modify_bid reuse this booking.
`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": {
-    "sessionId": {
-      "description": "Session id for place_bid / modify_bid / get_bid_status. Absent when the booking isn't bid-eligible.",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed2 schema fields changedSep 22, 2026

changedInput schema / properties / intentContext / properties / notes / description

Previous value: -"Short preference note, e.g. 'anniversary trip, wants lie-flat'. NEVER include booking references or names."New value: +"Short preference note, e.g. 'anniversary trip, wants lie-flat'. For privacy, leave out booking references and names."

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."

Changed1 schema field changedJul 15, 2026

addedInput schema / properties / intentContext

Added value: +{
+  "additionalProperties": false,
+  "description": "The traveler's stated shopping intent — bound to the session and surfaced back so offers are presented against it.",
+  "properties": {
+    "budgetAmount": {
+      "description": "Traveler's stated budget for the upgrade.",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "budgetCurrency": {
+      "description": "ISO currency for the budget, e.g. 'CAD'.",
+      "maxLength": 3,
+      "type": "string"
+    },
+    "notes": {
+      "description": "Short preference note, e.g. 'anniversary trip, wants lie-flat'. NEVER include booking references or names.",
+      "maxLength": 200,
+      "type": "string"
+    },
+    "preferredCabin": {
+      "enum": [
+        "BUSINESS",
+        "FIRST",
+        "PREMIUM_ECONOMY"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

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 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "sessionId": {
+      "description": "Session id for place_bid / modify_bid / get_bid_status. Absent when the booking isn't bid-eligible.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJul 2, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and non-idempotent, so the safety profile is partly covered. The description adds genuinely useful value by naming the response contents (eligibility status, upgrade options, bid ranges, session id), which discloses the stateful session creation implicitly; but calling it a 'lookup' slightly undersells the non-read-only nature the annotations flag.

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?

A single front-loaded sentence with the inputs first and the return payload second, with essentially no wasted words. It could have used a second short sentence for sibling routing without hurting brevity.

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?

For a 7-parameter, nested-object tool with no output schema, the description does well to enumerate the return shape. But in a sibling cluster of four-plus eligibility/session tools it leaves the agent without enough to disambiguate entry points, and it never states prerequisites or the booking-reference+last-name match requirement beyond restating inputs.

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 nested intentContext and conversationId is already documented in the schema. The description only gestures at 'booking reference and last name, and airline' and adds no format, privacy or session-binding detail beyond what the schema provides, so 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 (looks up), resource (a booking's upgrade eligibility) and the keying inputs (booking reference, last name, airline), plus what it returns. It does not, however, differentiate itself from near-name siblings such as start_eligibility_check, get_eligibility_result or mint_eligibility_session, so an agent could still pick the wrong entry point.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no mention of the alternative eligibility tools that crowd the sibling list. The only routing hint is the trailing 'session id for follow-up bid tools', which is about the next step rather than when this tool beats its siblings.

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?