Skip to main content
Glama

upgrade-agent

by ai.upgradeagent
OverviewDiscussionsAdmin

Place Upgrade Bid

place_bid

Places an upgrade bid, or buys a fixed-price (INSTANT) upgrade, for a checked booking. Takes an eligibility-check session id, an amount (omitted for INSTANT), and a cabin/segment. Returns a secure operator link to complete payment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNoBid amount in the offer currency (or points for POINTS). OMIT for INSTANT — the airline's fixed price is used automatically.
confirmNoSet true to confirm and commit a REAL bid submission (human-in-the-loop). Only required once live bid submission is enabled; otherwise the bid is staged for secure payment.
segmentNoRoute 'YUL-LHR' or flight number, if more than one segment is eligible.
quantityNoNumber of seats (default 1).
sessionIdNoThe sessionId from start_eligibility_check. Optional if conversationId is passed (reuses the last checked booking).
upgradeTypeNoTarget cabin, if the booking has more than one eligible option.
purchaseTypeNoBID (money offer, default), POINTS to redeem loyalty points ('amount' = points), or INSTANT to buy now at the airline's fixed price (no amount needed).
conversationIdNoStable conversation id used on get_eligibility_result — lets you bid without re-passing the sessionId.
presentationReportNoREPORT WHAT YOU SHOWED: if you filtered, hid, or deprioritized ANY offer from the eligibility result before presenting to the traveler, report every offer here with shown + reason. Contains no traveler data; powers partner analytics.

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": {
-    "amount": {
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "competitiveness": {
-      "anyOf": [
-        {
-          "additionalProperties": false,
-          "properties": {
-            "band": {
-              "description": "Which slice of the bid range the estimate reflects (low/mid/high/overall).",
-              "type": "string"
-            },
-            "confidence": {
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "probability": {
-              "description": "Historical acceptance rate for comparable bids (0–1).",
-              "type": "number"
-            },
-            "samples": {
-              "description": "Resolved outcomes behind the estimate.",
-              "type": "number"
-            }
-          },
-          "required": [
-            "probability",
-            "samples",
-            "band",
-            "confidence"
-          ],
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "Bid Analysis: acceptance odds for THIS bid, present only when enough resolved outcomes exist."
-    },
-    "currency": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "handoffUrl": {
-      "description": "Secure operator page to complete payment, when applicable.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "ok": {
-      "description": "Whether the bid was staged successfully.",
-      "type": "boolean"
-    },
-    "reasoningBricks": {
-      "description": "Model-legible reasons to present alongside the bid (Reasoning Bricks).",
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "kind": {
-            "type": "string"
-          },
-          "partner": {
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "source": {
-            "type": "string"
-          },
-          "text": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "kind",
-          "text",
-          "source",
-          "partner"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "stage": {
-      "description": "e.g. 'needs_payment' — where the bid is in the flow.",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Changed4 schema fields changed
    • changedInput schema / properties / amount / description
      Previous value: -"Bid amount in the offer currency."New value: +"Bid amount in the offer currency (or points for POINTS). OMIT for INSTANT — the airline's fixed price is used automatically."
    • changedInput schema / properties / purchaseType / description
      Previous value: -"BID (money offer, default) or POINTS to redeem loyalty points. For POINTS, 'amount' is the number of points."New value: +"BID (money offer, default), POINTS to redeem loyalty points ('amount' = points), or INSTANT to buy now at the airline's fixed price (no amount needed)."
    • changedInput schema / properties / purchaseType / enum
      Previous value: -[
-  "BID",
-  "POINTS"
-]New value: +[
+  "BID",
+  "POINTS",
+  "INSTANT"
+]
    • removedInput schema / required
      Removed value: -[
-  "amount"
-]
  3. Changed1 schema field changed
    • addedInput schema / properties / purchaseType
      Added value: +{
+  "description": "BID (money offer, default) or POINTS to redeem loyalty points. For POINTS, 'amount' is the number of points.",
+  "enum": [
+    "BID",
+    "POINTS"
+  ],
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / presentationReport
      Added value: +{
+  "description": "REPORT WHAT YOU SHOWED: if you filtered, hid, or deprioritized ANY offer from the eligibility result before presenting to the traveler, report every offer here with shown + reason. Contains no traveler data; powers partner analytics.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "offerId": {
+        "description": "The offer id from the eligibility result's 'Offer ids for presentation reporting' line.",
+        "type": "string"
+      },
+      "reason": {
+        "description": "Why it was filtered or deprioritized — supply when shown=false (over budget → REASON_PRICE_CEILING; low acceptance odds → REASON_LOW_PROBABILITY; conflicts with stated preferences → REASON_PREFERENCE_CLASH).",
+        "enum": [
+          "REASON_PRICE_CEILING",
+          "REASON_LOW_PROBABILITY",
+          "REASON_PREFERENCE_CLASH"
+        ],
+        "type": "string"
+      },
+      "shown": {
+        "description": "Whether you actually presented this offer to the traveler.",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "offerId",
+      "shown"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  5. Changed2 schema fields changed
    • addedOutput schema / properties / competitiveness
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "band": {
+          "description": "Which slice of the bid range the estimate reflects (low/mid/high/overall).",
+          "type": "string"
+        },
+        "confidence": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "probability": {
+          "description": "Historical acceptance rate for comparable bids (0–1).",
+          "type": "number"
+        },
+        "samples": {
+          "description": "Resolved outcomes behind the estimate.",
+          "type": "number"
+        }
+      },
+      "required": [
+        "probability",
+        "samples",
+        "band",
+        "confidence"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Bid Analysis: acceptance odds for THIS bid, present only when enough resolved outcomes exist."
+}
    • addedOutput schema / properties / reasoningBricks
      Added value: +{
+  "description": "Model-legible reasons to present alongside the bid (Reasoning Bricks).",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "kind": {
+        "type": "string"
+      },
+      "partner": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "source": {
+        "type": "string"
+      },
+      "text": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "text",
+      "source",
+      "partner"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "amount": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "currency": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "handoffUrl": {
+      "description": "Secure operator page to complete payment, when applicable.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ok": {
+      "description": "Whether the bid was staged successfully.",
+      "type": "boolean"
+    },
+    "stage": {
+      "description": "e.g. 'needs_payment' — where the bid is in the flow.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  7. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations are sparse: readOnlyHint=false, destroyHint=false, so the description carries the burden. It discloses that the call returns a secure operator link for payment, implies a multi-step flow, and clarifies the confirm parameter's role for real submissions. This goes beyond the schema, although it could mention test vs. production behavior more explicitly. Not a contradiction.

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?

The description is a single concise paragraph that front-loads the core action, then covers exclusions and payment flow. It is efficient and readable, though it packs many details; the key exclusions (INSTANT) are well placed, so it earns a 4 rather than a 5.

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 tool's high complexity (9 parameters, 3 purchase types, multiple workflows), the description covers the main paths and redirects to eligibility checks. However, it doesn't explain the confirm parameter's default behavior (staged vs live) in detail or the return structure of the operator link. With an output schema absent, a bit more detail would make it fully complete, but it is competent for an expert agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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, but the description adds crucial context: it explains the interplay between purchaseType and amount (omitted for INSTANT), the role of sessionId vs conversationId, and the strict business rule for presentationReport. This adds real semantic value beyond the schema properties.

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 clearly states the tool's dual purpose: placing an upgrade bid or buying an INSTANT upgrade. It names the resource (checked booking), the key modalities (BID, INSTANT, POINTS), and gives enough detail to distinguish it from related tools like modify_bid or cancel_bid.

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

Usage Guidelines5/5

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

The description explicitly tells when to place a bid or use INSTANT, references the required sessionId from start_eligibility_check, and clarifies that amount is omitted for INSTANT. It also mentions the operator payment link, signaling a follow-up action, so an agent understands when to call this tool versus alternatives.

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