Skip to main content
Glama

upgrade-agent

by ai.upgradeagent
OverviewDiscussionsAdmin

search_upgrade_options

Read-onlyIdempotent

Finds operators that offer upgrades. With an origin and destination airport (IATA codes, e.g. YUL and LHR) the result is route-level: carriers with observed upgrade pricing on that airport pair (per-cabin ranges from anonymized checks, either direction), carriers confirmed by operator inventory where that upstream is enabled, and carriers whose hub or home country is at one end of the route — the last group is labelled as a hub match that is not confirmed and carries no pricing. Without a route, the result is the operator list filtered by vertical, region, and/or product.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoOptional travel date (YYYY-MM-DD) — used for live inventory confirmation when that upstream is enabled.
cabinNoOptional: limit observed route pricing to one target cabin.
originNoOrigin airport IATA code (e.g. 'YUL'). With destination, filters to that route.
regionNo
productNo
verticalNo
destinationNoDestination airport IATA code (e.g. 'LHR'). With origin, filters to that route.
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. Changed5 schema fields changed
    • addedInput schema / properties / cabin
      Added value: +{
+  "description": "Optional: limit observed route pricing to one target cabin.",
+  "enum": [
+    "BUSINESS",
+    "FIRST",
+    "PREMIUM_ECONOMY"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / date
      Added value: +{
+  "description": "Optional travel date (YYYY-MM-DD) — used for live inventory confirmation when that upstream is enabled.",
+  "type": "string"
+}
    • changedInput schema / properties / destination / description
      Previous value: -"Destination city/airport (informational only — not used to route-filter)."New value: +"Destination airport IATA code (e.g. 'LHR'). With origin, filters to that route."
    • changedInput schema / properties / origin / description
      Previous value: -"Origin city/airport (informational only — not used to route-filter)."New value: +"Origin airport IATA code (e.g. 'YUL'). With destination, filters to that route."
    • 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
    • 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 / 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"
+}
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description layers on substantive behavioral detail: the third carrier group is flagged as an unconfirmed hub match carrying no pricing, and pricing comes from anonymized checks in either direction. This provenance/labeling context is info an agent needs to interpret results correctly.

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?

Front-loaded with the core purpose, then two parallel mode branches. It is dense and clause-heavy with multiple em-dashes, but nearly every clause carries information about the result composition rather than filler.

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 8 optional parameters, no output schema, and closed-world annotations, the description does the heavy lifting by explaining what each of the three carrier groups in the route result means. It stops short of clarifying pagination/limits or how region/vertical/product interact without a route.

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 63%, and the schema already documents date, cabin, origin, destination, and travelerQuestion. The description's only incremental parameter insight is that route results are computed 'either direction' and that date drives live inventory confirmation, which the schema largely already states. Baseline 3 is appropriate.

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 opens with a specific verb and resource ('Finds operators that offer upgrades') and then clearly delineates two operating modes (route-level vs. operator list). It distinguishes itself from siblings by scope, though it never names an alternative tool like get_upgrade_pricing or list_partners.

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

Usage Guidelines4/5

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

The two branches ('With an origin and destination airport...' and 'Without a route...') give explicit conditions for the two modes, which is real when-to-use guidance. However, it never names an alternative tool or states when a sibling such as get_upgrade_pricing should be preferred instead.

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