Skip to main content
Glama
Sign In

cwsi.net Fare Classes & Mileage Calculators

by net.cwsi
OverviewDiscussionsAdmin

Malaysia Airlines Enrich Points and Elite Points Calculator

calculate_malaysia_airlines_enrich_points
Read-onlyIdempotent

Malaysia Airlines Enrich Points and Elite Points for a Malaysia Airlines ticket. Enrich Points = the fare in Malaysian Ringgit (MYR: base fare plus fuel surcharge and administration charge, no government taxes, whole ticket) x tier rate (Blue 1.5, Silver 1.8, Gold 2.2, Platinum 2.5), rounded down. Malaysia Airlines converts a fare in another currency itself and does not publish the rate, so give the MYR amount. Elite Points are fixed per flight by distance zone and cabin (Economy 1 to 10, Business Class 2 to 15, Business Suite 3 to 20), worked out only for a flight to or from Kuala Lumpur (KUL): Malaysia Airlines does not say how another flight is zoned, so it is shown as not worked out. Progress toward Silver (35), Gold (70) and Platinum (140) Elite Points in a calendar year; ep is the Elite Points so far. Give segs: one entry per one-way flight, in order, with its great-circle miles (calculate_flight_distance gives them), the ISO country codes of its two airports, from and to IATA airport codes (needed for Elite Points) and optionally its own cabin (Y, C or S). Uses cwsi.net's calculator and the airline's published rules. Give the price in MYR, not US dollars. Unofficial.

Input Schema

NameRequiredDescriptionDefault
epNoElite Points you have this calendar year (optional). Used only for the progress toward the next tier.
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 cabin (Y, C, S) for a flight in another cabin than the ticket's; 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).
tierNoYour Enrich tier. BL = Blue (1.5 per MYR 1); SL = Silver (1.8 per MYR 1); GD = Gold (2.2 per MYR 1); PT = Platinum (2.5 per MYR 1). Sets the Enrich Points per MYR 1. Silver is oneworld Ruby, Gold is Sapphire and Platinum is Emerald.BL
tripNoTrip. ow = One way; rt = Round trip. Round trip counts the same flights back the other way for Elite Points. The fare above is for the whole ticket either way.ow
cabinNoCabin. Y = Economy; C = Business Class; S = Business Suite. Business Suite is the A350 suite product.Y
priceNoTicket fare in MYR (whole trip) in MYR. In Malaysian Ringgit: the base fare plus the fuel surcharge and administration charge, without government taxes and fees, for the whole ticket. Malaysia Airlines converts a fare paid in another currency itself and does not publish the rate. Required unless creditTo is given.
creditToNoCredit the flights to a partner program instead of Malaysia Airlines's own: american = American AAdvantage (creditStatus one of: AAdvantage member, AAdvantage Gold, AAdvantage Platinum, AAdvantage Platinum Pro, AAdvantage Executive Platinum); alaska = Atmos Rewards (creditStatus one of: Atmos Rewards member, Atmos Silver, Atmos Gold, Atmos Platinum, Atmos Titanium); flying-blue = Flying Blue (creditStatus one of: Explorer, Silver, Gold, Platinum, Ultimate); ba-club = British Airways Club (creditStatus one of: Blue, Bronze, Silver, Gold). 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. No price is needed with creditTo.
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.5/5.0
Behavior5/5

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

Annotations already establish a safe, idempotent, read-only calculation, and the description goes well beyond them: the exact formula (MYR fare x tier rate, rounded down), the KUL-only zoning rule and the fact that other flights are returned as 'not worked out', the calendar-year tier thresholds, and the 'Unofficial' provenance note. That is meaningful behavioral context an agent could not infer from 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?

Front-loaded with the points formula, which is the right lead, and it contains little pure filler. However it is a single dense run-on block with no structure, and it repeats schema content (tier multipliers, the definition of price) that the parameter descriptions already carry.

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?

For a 10-parameter tool the description covers the calculation rules, the currency requirement, the geographic restriction on Elite Points, the per-segment input contract, and the tool it depends on; an output schema exists so return values need not be described. The only omission is the partner-credit path, which the creditTo schema description fully documents.

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 description coverage is 100%, so a 3 is the baseline, and the description does add value on top: it fixes the unit and composition of price (base fare + fuel surcharge + admin charge, no taxes, whole ticket), explains segs ordering and its optional per-flight cabin, and points to calculate_flight_distance for miles. It leaves the creditTo/creditClass/creditStatus partner-crediting mode entirely to the schema.

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?

States a specific verb and resource ('Malaysia Airlines Enrich Points and Elite Points for a Malaysia Airlines ticket') and immediately scopes it to one airline, which separates it from the ~50 sibling calculate_*_miles tools. It also names its dependency (calculate_flight_distance supplies the miles), so an agent knows exactly what this tool does and what it needs.

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?

Gives real usage constraints: give the fare in MYR not USD (the airline converts foreign-currency fares itself and does not publish the rate), Elite Points are only computed for flights to/from KUL, and segs must be one entry per one-way flight in order. It does not explicitly frame when to prefer this over a sibling or over the partner-credit path, so it stops short of an explicit when/when-not statement.

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

All cwsi.net Fare Classes & Mileage Calculators 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