Skip to main content
Glama

cwsi.net Fare Classes & Mileage Calculators

Vietnam Airlines Lotusmiles Calculator

calculate_vietnam_airlines_miles
Read-onlyIdempotent

Vietnam Airlines Lotusmiles award miles, tier miles and tier segments for Vietnam Airlines flights (rates from 26 August 2026). Award miles = distance x fare family rate (fam: Business Flex 200%, Business Classic 150, Premium Economy Flex 130, Premium Economy Classic 120, Economy Flex 110, Economy Classic 80 within Vietnam and 65 abroad, Economy Lite 60 and 25, Economy Super Lite 10), rounded down per flight; Vietnam Airlines prints the rates as decimals (2.00), read as multipliers of the miles flown. Tier miles are the award miles without the tier bonus (Economy Super Lite earns none); tier segments per flight by fare family and distance band. The Titanium 30%, Gold 50% and Platinum or Million Miler 100% bonus adds award miles only. Progress toward Titanium (15,000 tier miles or 20 segments), Gold (30,000 or 30) and Platinum (50,000 or 50) in 12 months; tm and ts are the totals so far. Give segs: one entry per one-way flight, in order, with its great-circle miles (calculate_flight_distance gives them) and the ISO country codes of its two airports (both VN = domestic rate). Takes no price. Uses cwsi.net's calculator and the airline's published rules. Unofficial.

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": {
      "segs": "<segs>"
    },
    "name": "calculate_vietnam_airlines_miles"
  }
}

Input Schema

NameRequiredDescriptionDefault
tmNoTier miles you have in your 12-month period (optional). Used only for the progress toward the next tier.
tsNoTier segments you have in your 12-month period (optional). Some fares count half a segment.
famNoFare family. BF = Business Flex (Business, J, C); BC = Business Classic (Business, D, I); PF = Premium Economy Flex (Premium Economy, W); PC = Premium Economy Classic (Premium Economy, Z, U); EF = Economy Flex (Economy, Y, M, B); EC = Economy Classic (Economy, S, H, K, L); EL = Economy Lite (Economy, Q, N, R, T, E); ES = Economy Super Lite (Economy, A, P, G). The fare family on your ticket, or its booking class in brackets. Booking class Q on routes between Vietnam and Europe, Australia, the United States or China counts as Economy Classic.EC
segsYesThe flights, one way and in order, one entry per flight (1 to 8): fromCountry and toCountry, the ISO 3166 two-letter country codes of its two airports; miles, its great-circle distance in miles (1 to 12,500); optional from and to, the IATA codes of its two airports, which label the breakdown; some airlines also use them (Vladivostok, VVO, on JAL and ANA; the Madrid-Barcelona Air Shuttle, MAD-BCN, on Iberia; the long-haul tables named by city on SAS).
tripNoTrip. ow = One way; rt = Round trip. Round trip counts the same flights back the other way.ow
statusNoYour Lotusmiles tier. NO = Registration; SI = Silver; TI = Titanium (+30%); GO = Gold (+50%); PL = Platinum (+100%); MM = Million Miler (+100%). The tier bonus is paid on award miles for Vietnam Airlines flights; it does not count toward tier miles or segments.NO
creditToNoCredit the flights to a partner program instead of Vietnam Airlines's own: delta = Delta SkyMiles (creditStatus one of: SkyMiles Member, Silver Medallion, Gold Medallion, Platinum Medallion, Diamond Medallion); flying-club = Flying Club (creditStatus one of: Red, Silver, Gold); flying-blue = Flying Blue (creditStatus one of: Explorer, Silver, Gold, Platinum, Ultimate). Earns by each flight's distance and the booking class at the program's published partner rates; leave creditTo out for the airline's own program. Give the booking class letter as creditClass. The flights are segs (their miles), or creditFlights.
creditClassNoThe booking class letter on the ticket, for creditTo (required with creditTo). Ignored without creditTo.
creditStatusNoYour status in the creditTo program, by its name as listed under creditTo. Defaults to the base level. Ignored without creditTo.
creditFlightsNoThe flights for creditTo: one entry per one-way flight, in order, with its great-circle miles (calculate_flight_distance gives them) and optionally from/to airport codes. Defaults to segs when they carry miles.

Output Schema

NameRequiredDescriptionDefault
linkYes
notesYes
inputsYes
airlineYes
headlineYes
progressNo
breakdownYes
calculatorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Despite annotations already declaring a safe read-only/idempotent profile, the description adds substantial behavior: award miles are rounded down per flight, the tier bonus applies only to award miles and not to tier miles/segments, tier progress thresholds over 12 months, and an explicit 'Unofficial' disclaimer plus the data source. This is rich context beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense and nearly every clause carries information, but it is delivered as one long run-on paragraph with no structure, making the rate table and the counter-intuitive 'tier bonus adds award miles only' rule hard to scan. For a 10-parameter tool some length is warranted, but the presentation is not front-loaded beyond the first sentence.

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 an output schema present, return values need not be described, and the description covers the calculation rules, tier-progress semantics, eligible creditTo programs with their status names, and the unofficial-data caveat. It does not spell out error behavior for mismatched creditClass/creditTo, but the coverage is otherwise solid for a tool of this 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?

Schema coverage is 100%, so baseline is 3, but the description genuinely adds meaning: the full fare-family rate table (200%/150/130/...) that the schema only abbreviates as BF/BC/etc., the rule that both-VN airports trigger the domestic rate, the note that rates are printed as decimals read as multipliers, and that tm/ts are totals so far. The segs/from-to explanation partly restates the schema, capping this at 4.

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 opening sentence names a specific verb+resource+scope: Lotusmiles award miles, tier miles and tier segments for Vietnam Airlines flights. It also fixes the effective rate date (26 August 2026), so an agent knows exactly what is being computed. Distinction from the ~50 sibling calculators is carried by the airline name, which is stated repeatedly.

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?

It gives clear context: feed segs with great-circle miles obtained from calculate_flight_distance, and leave creditTo out to use Vietnam Airlines's own program while supplying creditClass when crediting to a partner. There are no explicit when-not-to-use statements or sibling comparisons, but the usage conditions are clear.

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