Skip to main content
Glama

Flat Flights — business & first class fares

Cash vs points/miles & credit-card transfer paths for Business Class

cash_vs_miles_options
Read-only

Business class miles & credit card transfer calculator: compares today’s cheapest cash fare on Aviasales with published/derived saver award bands across 19 airline programs (Avios, Flying Blue, Aeroplan, KrisFlyer, Miles & More, ANA, Skywards…) and 43 bank point programs (Amex, Chase, Citi, Capital One, Bilt, Revolut…), returning cents-per-mile value and the cash booking link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "cash_vs_miles_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesCity name (e.g. "Milan", "New York") or 3-letter IATA city/airport code (e.g. "MIL", "JFK").
fromYesCity name (e.g. "Milan", "New York") or 3-letter IATA city/airport code (e.g. "MIL", "JFK").
card_marketNoOptional 2-letter country code to filter credit card transfer partners (US, GB, DE, FR, IT, ES, CA, AU, SG, HK, AE, IN, JP, BR).

Output Schema

NameRequiredDescriptionDefault
intelYes
routeYes
cashFareEurNo
cashBookingLinkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds meaningful behavior beyond that: it discloses the data sources (Aviasales live cash fares, published/derived award bands), the breadth of program coverage, and the derived output metric. It omits anything about fare volatility, latency, or how 'derived' bands should be treated as estimates.

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?

A single front-loaded sentence that leads with the calculator's function before listing program coverage. The parenthetical program enumerations are long but carry real scope information; minor trimming of the ellipsis lists would tighten it further.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is not required, and annotations handle the safety profile. The description still supplies the one thing an agent needs to judge trustworthiness: that cash fares are live and award bands may be derived rather than actual availability.

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 all three parameters including card_market's country-code filtering are already documented in the schema. The description adds no syntax, format, or defaulting detail beyond that; the baseline of 3 applies when the schema does the heavy lifting.

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 names a specific verb and resource: it compares today's cheapest cash fare from Aviasales against saver award bands across 19 airline programs and 43 bank programs, returning cents-per-mile value plus a cash booking link. That scope (points/miles valuation, not fare search) cleanly distinguishes it from siblings such as search_business_class_fares or cheapest_business_class_to.

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 use case is clear from context: call this when the question is whether to pay cash or redeem miles/points for business class. However, it never states exclusions or names an alternative for pure fare lookups, so the agent must infer the boundary from the sibling names rather than from the text.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources