upgrade-agent

Start Eligibility Check

start_eligibility_check

Starts an upgrade eligibility check for a flight, cruise, or rail booking. Returns a secure page (and, where supported, an inline form) for the traveler to enter their booking reference and last name.

Input Schema

TableJSON Schema

Name	Required	Description
`carrier`	No	Airline/cruise/rail name or IATA code if known (e.g. 'Air Canada' or 'AC').
`language`	No	ISO 639-1 language for the page/offer (e.g. 'fr', 'es'). Defaults to 'en'.
`intentContext`	No	The traveler's stated shopping intent — bound to the session and surfaced back so offers are presented against it.
`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 Upgrade Agent's answers over time.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026

changedOutput schema / (root)

Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "carrier": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "carrierAccent": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "carrierIata": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "carrierLogo": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "carrierName": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "sessionId": {
-      "description": "Secure eligibility session id — pass to get_eligibility_result.",
-      "type": "string"
-    },
-    "url": {
-      "description": "Secure /e/ link the traveler can open to enter their details.",
-      "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": {
+    "carrier": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "carrierAccent": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "carrierIata": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "carrierLogo": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "carrierName": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sessionId": {
+      "description": "Secure eligibility session id — pass to get_eligibility_result.",
+      "type": "string"
+    },
+    "url": {
+      "description": "Secure /e/ link the traveler can open to enter their details.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJul 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The annotations are all false booleans and provide no real safety profile, so the description carries most of the burden. It adds useful behavior by saying the tool returns a secure page/form and delegates booking-reference entry to the traveler, but it does not disclose side effects, session creation, idempotency, or what happens after the page is returned.

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 front-loaded sentences with no filler: the first names the action and scope, the second explains the return experience. The parenthetical about inline forms is a useful qualifier, not waste.

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 more fully specify the return value (e.g., URL vs. HTML vs. session reference) and how the result relates to later tools like check_upgrade_eligibility or get_eligibility_result. It covers the high-level flow but not enough for an agent to integrate the response reliably.

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 the baseline is 3 and the input schema already explains carrier, language, intentContext, and travelerQuestion with examples. The description adds no parameter-level information; it only describes the overall flow.

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 uses a specific verb ('Starts') and resource ('upgrade eligibility check'), scopes it to flight/cruise/rail bookings, and distinguishes the tool from siblings by noting it returns a traveler-facing secure page rather than an eligibility verdict. This makes its role clear without opening sibling schemas.

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?

It gives a domain window (flight, cruise, or rail) but no explicit when-to-use or when-not-to-use guidance, and it never names the sibling tools like check_upgrade_eligibility or get_eligibility_result that an agent must choose between. The intended use is only implied by the verb 'Starts'.

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?