Skip to main content
Glama

upgrade-agent

by ai.upgradeagent
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
carrierNoAirline/cruise/rail name or IATA code if known (e.g. 'Air Canada' or 'AC').
languageNoISO 639-1 language for the page/offer (e.g. 'fr', 'es'). Defaults to 'en'.
intentContextNoThe traveler's stated shopping intent — bound to the session and surfaced back so offers are presented against it.
travelerQuestionNoThe 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.

  1. Changed1 schema field changed
    • 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."
  2. Changed1 schema field changed
    • 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
  3. Changed2 schema fields changed
    • 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."
  4. Changed1 schema field changed
    • 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"
+}
  5. Changed1 schema field changed
    • 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"
+}
  6. Changed1 schema field changed
    • 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"
+}
  7. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations mark this as non-read-only and non-idempotent, so the agent knows it initiates stateful work. The description adds genuinely useful context beyond that: the tool does not itself collect PII but hands off to a secure page where the traveler enters booking reference and last name, and the inline form is only available 'where supported'.

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: purpose first, returned artifact second. Every clause earns its place.

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?

With no output schema, the description correctly takes on the burden of describing the return value (a secure page plus optional inline form), which is the key thing an agent needs. It stops short of explaining the session/lifecycle relationship to get_eligibility_result or mint_eligibility_session, but for a session-initiating tool this is largely adequate.

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 carrier, language, intentContext, and travelerQuestion thoroughly, including privacy caveats. The description adds no parameter-level meaning and notably does not clarify that booking reference/last name are entered on the returned page rather than passed as arguments, which is a missed opportunity.

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 and resource ('starts an upgrade eligibility check') and names the supported domains (flight, cruise, rail). It also discloses the artifact returned (a secure page/inline form). However, it does not distinguish itself from nearby siblings such as check_upgrade_eligibility or mint_eligibility_session, leaving the agent to infer the difference.

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 or when-not-to-use guidance, and no alternative is named despite at least three closely related eligibility tools in the sibling list. Usage is only implied by the 'start' verb.

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

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