Skip to main content
Glama

cwsi.net Fare Classes & Mileage Calculators

Shenzhen Airlines PhoenixMiles Calculator

calculate_shenzhen_airlines_miles
Read-onlyIdempotent

Shenzhen Airlines PhoenixMiles mileage (in kilometres) and qualifying segments for Shenzhen Airlines flights. PhoenixMiles is the Air China group programme (calculate_air_china_miles covers Air China flights). Mileage = distance in km (the great-circle miles x 1.609344; PhoenixMiles uses the IATA distance) x booking-class % (25% to 300%), at least 800 km in Business (J, C, D, Z, R) and 500 in Premium Economy and Economy; where Shenzhen prints two rates (J, R, B, U), the first is a flight within Mainland China (both airports CN) and the second an international or regional flight. Classes I, X and N earn nothing. The 25/30/50% elite bonus is a note only, and the flight is not added to the progress (PhoenixMiles does not say whether qualifying kilometres equal the mileage earned). Cards need Silver 40,000, Gold 80,000 or Platinum 160,000 qualifying km, or 25 / 40 / 90 qualifying segments, in 12 months; qk and qs are the member's own totals so far, used only for the progress. 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. Takes no price. Uses cwsi.net's calculator and the airline's published rules. Unofficial.

Input Schema

NameRequiredDescriptionDefault
qkNoQualifying kilometres you have in the last 12 months (optional). Used only for the progress toward the next card; the flight is not added.
qsNoQualifying segments you have in the last 12 months (optional). Segments can be fractions, for example 1.1 in Y. Used only for the progress toward the next card; the flight is not added.
clsNoBooking class. J = J (Business 300% / 250%); C = C (Business 200%); D = D (Business 150%); Z = Z (Business 125%); R = R (Business 110% / 125%); G = G (Premium Economy 110%); E = E (Premium Economy 90%); Y = Y (Economy 110%); B = B (Economy 100% / 110%); M = M (Economy 100%); U = U (Economy 100% / 75%); H = H (Economy 75%); Q = Q (Economy 75%); V = V (Economy 75%); W = W (Economy 50%); S = S (Economy 50%); T = T (Economy 50%); L = L (Economy 25%); K = K (Economy 25%); P = P (Economy 25%); A = A (Economy 25%); I = I (earns nothing); X = X (earns nothing); N = N (earns nothing). The letter on your Shenzhen Airlines ticket. A class with two percentages pays the first on flights within Mainland China and the second on international and regional flights.Y
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 PhoenixMiles card. NO = Not an elite member; SI = Silver (+25%); GO = Gold (+30%); PL = Platinum (+50%). Elite members earn extra mileage on Air China group flights. It is shown as a note, not added, because PhoenixMiles does not say what it is a percentage of.NO
creditToNoCredit the flights to a partner program instead of Shenzhen Airlines's own: united = United MileagePlus (creditStatus one of: General member, Premier Silver, Premier Gold, Premier Platinum, Premier 1K); aeroplan = Aeroplan (creditStatus one of: Aeroplan Member, 25K, 35K, 50K, 75K, Super Elite). 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. The booking class is cls (or creditClass). The flights are segs (their miles), or creditFlights.
creditClassNoThe booking class letter for creditTo, when it differs from the class question. 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.0
Behavior4/5

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

With annotations covering the safety profile (readOnly, idempotent, non-destructive, closed-world), the description adds substantial behavioral context: the earning formula, floor minimums (800 km Business, 500 PE/Economy), the domestic-vs-international dual-rate rule, classes that earn nothing, the elite bonus being note-only, card thresholds, and the 'Unofficial' sourcing caveat. This goes well beyond the annotations, though return-format behavior is left to the output schema.

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 purpose is front-loaded, but the body is a dense run-on paragraph that heavily duplicates information already in the schema (full class percentage tables, the segs field layout). Much of this does not earn its place given 100% schema coverage, weakening overall conciseness despite a solid opening.

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 10-parameter calculation tool with a rich schema and an output schema present, the description supplies the domain rules an agent needs (formula, minimums, elite bonus semantics, card thresholds) and an unofficial-source caveat. Completeness is high; the only gap is that return values are rightly delegated to the output schema.

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 is 3 and the schema already documents every parameter including the class percentages and segs structure. The description largely restates schema content (class lists, percentage tables, seg fields) rather than adding new per-parameter meaning, so it does not rise above the baseline.

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 ('calculates Shenzhen Airlines PhoenixMiles mileage in kilometres and qualifying segments for Shenzhen Airlines flights') and explicitly differentiates from the sibling calculate_air_china_miles by naming it and its scope. An agent can distinguish these two Air China group tools without opening either schema.

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?

Provides clear context for when this applies (Shenzhen Airlines flights, PhoenixMiles programme) and routes to the Air China variant for Air China flights, plus describes the creditTo partner-programme alternative. It stops short of explicit when-not/exclusion language for edge cases, but the sibling routing and programme scoping are strong.

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