upgrade-agent

search_upgrade_options

Read-onlyIdempotent

Find operators that offer upgrades, filtered by vertical, region, and/or product. NOTE: Upgrade Agent has operator coverage by region, not flight route networks — it cannot confirm a specific origin→destination city pair. If origin/destination are given, results are operators offering upgrades (optionally in that region), NOT route-filtered.

Input Schema

TableJSON Schema

Name	Required	Description
`origin`	No	Origin city/airport (informational only — not used to route-filter).
`region`	No
`product`	No
`vertical`	No
`destination`	No	Destination city/airport (informational only — not used to route-filter).
`travelerQuestion`	No	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.

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds behavioral transparency by noting the tool cannot confirm city-pair routes, which is critical context not in 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?

The description is two concise sentences plus a note, with no wasted words. It front-loads the main purpose and adds critical caveats efficiently.

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?

For a search tool with 6 parameters and no output schema, the description explains filtering behavior and limitations. It omits result format or pagination but is otherwise complete for the tool's complexity.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While schema coverage is 50%, the description clarifies that origin and destination are informational-only (reinforcing schema descriptions). It also highlights that vertical, region, and product are the primary filters, compensating for missing schema descriptions on other parameters.

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 purpose: 'Find operators that offer upgrades, filtered by vertical, region, and/or product.' It identifies the verb (find) and resource (operators offering upgrades), and the note distinguishes from route-based tools.

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 description provides explicit usage context: when to use (finding upgrade operators with filters) and when not (if route confirmation is needed). It explains that origin/destination are informational and not route-filtered, guiding proper use without naming 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 tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct function or workflow step (e.g., general info vs booking-specific check, bid placement vs bid status, partner lookup vs pricing), and descriptions clarify when to use which. Even overlapping actions like check_upgrade_eligibility and start_eligibility_check are clearly differentiated by context.

Naming Consistency4/5

Most tools follow a verb_noun pattern (e.g., check_upgrade_eligibility, place_bid, get_bid_status). A few deviate slightly (partner_question_insights, usage_totals) but the naming is still intuitive and readable overall.

Tool Count4/5

17 tools is at the upper end of typical but still well-scoped given the breadth of functionalities (eligibility, bidding, watch, partner info, analytics). Every tool has a clear purpose, so the count feels justified rather than bloated.

Completeness4/5

The tool set covers the full lifecycle of upgrade management: eligibility check, bid placement/modification/status, pricing, partner info, watch, and system metrics. A minor gap is the absence of a cancel bid tool, but the main workflows are complete.

Resources

Need Help?