Skip to main content
Glama

upgrade-agent

by ai.upgradeagent
OverviewDiscussionsAdmin

get_upgrade_pricing

Read-onlyIdempotent

Returns typical upgrade bid ranges (low / typical / high, per cabin) for an operator, aggregated from anonymized eligibility checks. Accepts an IATA code or a name. Says so when there isn't enough observed data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cabinNoOptional: limit to one target cabin.
carrierNoOperator IATA code or name, e.g. 'LH' or 'Lufthansa'. Optional if conversationId carries the operator from earlier.
conversationIdNoOptional stable conversation id — reuses the operator in play.
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
    • 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."
  2. 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"
+}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark readOnlyHint, idempotentHint, and destructiveHint, so the description's extra context counts: it discloses that values are aggregated from anonymized eligibility checks and that insufficient data is reported rather than hidden. This adds meaningful behavioral detail beyond the structured annotations.

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, no filler: the first sentence carries the core return and source, and the second covers input flexibility and the insufficient-data behavior. Each sentence adds distinct information and is front-loaded.

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 no output schema, the description does describe the output shape (low/typical/high per cabin) and low-data behavior, and the schema covers all four optional parameters. It could more explicitly state that carrier or conversationId is needed, but the description's input hints plus schema make for a mostly complete picture.

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 applies; the description's only param-relevant note is 'Accepts an IATA code or a name,' which mostly restates the carrier schema description. No new parameter semantics beyond the schema are provided.

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 states exactly what the tool returns ('typical upgrade bid ranges (low / typical / high, per cabin) for an operator') and the source of aggregation, making it clearly distinct from sibling tools like place_bid or get_price_breakdown. The verb 'Returns' plus specific resource and output shape gives clear 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?

There is no explicit when-to-use or alternative routing like 'use get_price_breakdown for...' present; however, the purpose itself implies using it when typical bid ranges are needed. It does give some practical input guidance ('Accepts an IATA code or a name') and a low-data behavior note, so there is a weak usage context rather than none.

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