Skip to main content
Glama

upgrade-agent

by ai.upgradeagent
OverviewDiscussionsAdmin

Check Booking Eligibility

check_upgrade_eligibility

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pnrYesThe booking reference or PNR (e.g. ABC123).
carrierNoAirline/cruise/rail name or IATA code (e.g. 'SWISS' or 'LX').
languageNoISO 639-1 language for the offer page (e.g. 'fr', 'es'). Defaults to 'en'.
lastNameYesPassenger last name, exactly as it appears on the booking.
intentContextNoThe traveler's stated shopping intent — bound to the session and surfaced back so offers are presented against it.
conversationIdNoOptional stable conversation id — lets place_bid/modify_bid reuse this booking.
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 Upgrade Agent's answers over time.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already signal open-world, non-read-only, non-idempotent behavior. The description adds that the tool returns a session id for follow-up bid tools, which implies a stateful side effect beyond a pure lookup. It does not detail side effects or external calls, but the annotations carry the safety profile, so this is adequate.

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 sentences with no filler. The action, inputs, outputs, and downstream purpose are front-loaded, making the definition easy to scan and act on.

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 the rich schema with 100% parameter coverage and an absent output schema, the description sufficiently explains what the tool returns and why it matters. It leaves out how optional context fields should be used, but that burden is already carried by the schema.

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 baseline is 3. The description restates three inputs (booking reference, last name, airline) but adds no new meaning beyond the schema, and it says nothing about language, intentContext, conversationId, or travelerQuestion.

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?

The description states a specific verb and resource ('Looks up a booking's upgrade eligibility') and names the key inputs and outputs. It stops short of a 5 because it does not explicitly differentiate this from siblings like start_eligibility_check or get_eligibility_result, which appear to overlap in purpose.

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?

The description implies the tool should be used to check eligibility before follow-up bid tools, since it returns a session id for them. However, it gives no explicit when-to-use or when-not-to-use guidance and does not name alternative sibling tools, so the usage signal is only implicit.

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