cwsi.net Fare Classes & Mileage Calculators

Turkish Airlines Miles and Status Miles Calculator

calculate_turkish_airlines_miles

Read-onlyIdempotent

Turkish Airlines Miles&Smiles Miles and Status Miles. International flights: Miles = distance x booking-class rate with a minimum per class (Economy 25% to 125%; Business 135% or 150% on the Classic card, 160% or 175% on Classic Plus, Elite and Elite Plus); flights within Turkiye (both airports TR) earn fixed Miles by class. Status Miles = the same flights at the Classic card rate. Progress toward Classic Plus (25,000), Elite (40,000) and Elite Plus (80,000) Status Miles in 12 months; sm is the Status Miles 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. Takes no price. Uses cwsi.net's calculator and the airline's published rules. Unofficial.

Input Schema

Name	Required	Description	Default
`sm`	No	Status Miles you have in the last 12 months (optional). Used only for the progress toward the next tier.
`cls`	No	Booking class. C = C (Business 150% (175%)); D = D (Business 150% (175%)); K = K (Business 135% (160%)); J = J (Business 135% (160%)); Z = Z (Business 135% (160%)); Y = Y (Economy 125%); B = B (Economy 125%); M = M (Economy 100%); H = H (Economy 100%); S = S (Economy 100%); E = E (Economy 100%); Q = Q (Economy 100%); A = A (Economy 100%); O = O (Economy 100%); T = T (Economy 50%); L = L (Economy 50%); V = V (Economy 50%); G = G (Economy 50%); W = W (Economy 25%); P = P (Economy 25%); F = F (Economy 25%); U = U (Economy 25%). The letter on your ticket. Turkish Airlines has no First class: F is an Economy class here. Business shows the Classic rate, then the Classic Plus and higher rate.	M
`segs`	Yes	The 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).
`trip`	No	Trip. ow = One way; rt = Round trip. Round trip counts the same flights back the other way.	ow
`status`	No	Your Turkish Airlines tier. CL = Classic; CP = Classic Plus; EL = Elite; EP = Elite Plus. Classic Plus, Elite and Elite Plus earn more in Business. Economy earns the same on every card.	CL
`creditTo`	No	Credit the flights to a partner program instead of Turkish 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.
`creditClass`	No	The booking class letter for creditTo, when it differs from the class question. Ignored without creditTo.
`creditStatus`	No	Your status in the creditTo program, by its name as listed under creditTo. Defaults to the base level. Ignored without creditTo.
`creditFlights`	No	The 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

Name	Required	Description	Default
`link`	Yes
`notes`	Yes
`inputs`	Yes
`airline`	Yes
`headline`	Yes
`progress`	No
`breakdown`	Yes
`calculator`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 13, 2026

addedInput schema / properties / creditClass

Added value: +{
+  "description": "The booking class letter for creditTo, when it differs from the class question. Ignored without creditTo.",
+  "pattern": "^[A-Za-z]$",
+  "type": "string"
+}

addedInput schema / properties / creditFlights

Added value: +{
+  "description": "The 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.",
+  "items": {
+    "properties": {
+      "from": {
+        "description": "The departure airport's code; labels the breakdown.",
+        "pattern": "^[A-Za-z0-9]{3,4}$",
+        "type": "string"
+      },
+      "miles": {
+        "description": "Great-circle distance of this flight in miles.",
+        "maximum": 12500,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "to": {
+        "description": "The arrival airport's code; labels the breakdown.",
+        "pattern": "^[A-Za-z0-9]{3,4}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "miles"
+    ],
+    "type": "object"
+  },
+  "maxItems": 8,
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / creditStatus

Added value: +{
+  "description": "Your status in the creditTo program, by its name as listed under creditTo. Defaults to the base level. Ignored without creditTo.",
+  "maxLength": 64,
+  "type": "string"
+}

addedInput schema / properties / creditTo

Added value: +{
+  "description": "Credit the flights to a partner program instead of Turkish 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.",
+  "enum": [
+    "united",
+    "aeroplan"
+  ],
+  "type": "string"
+}

Changed3 schema fields changedOct 13, 2026

changedInput schema / properties / segs / description

Previous value: -"The 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)."New value: +"The 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)."

changedInput schema / properties / segs / items / properties / from / description

Previous value: -"The departure airport's IATA code, e.g. SYD. Labels the breakdown; JAL and ANA use it to spot Vladivostok (VVO), Qantas to pick its route tables, and Iberia to spot the Madrid-Barcelona Air Shuttle (MAD, BCN)."New value: +"The departure airport's IATA code, e.g. SYD. Labels the breakdown; JAL and ANA use it to spot Vladivostok (VVO), Qantas to pick its route tables, Iberia to spot the Madrid-Barcelona Air Shuttle (MAD, BCN), and SAS to pick its long-haul tables (named by city)."

changedInput schema / properties / segs / items / properties / to / description

Previous value: -"The arrival airport's IATA code, e.g. SYD. Labels the breakdown; JAL and ANA use it to spot Vladivostok (VVO), Qantas to pick its route tables, and Iberia to spot the Madrid-Barcelona Air Shuttle (MAD, BCN)."New value: +"The arrival airport's IATA code, e.g. SYD. Labels the breakdown; JAL and ANA use it to spot Vladivostok (VVO), Qantas to pick its route tables, Iberia to spot the Madrid-Barcelona Air Shuttle (MAD, BCN), and SAS to pick its long-haul tables (named by city)."

AddedOct 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish the safe/idempotent read profile, and the description adds real value beyond them: it discloses the data source ('cwsi.net's calculator and the airline's published rules') and flags the result as 'Unofficial.' It also exposes the earning model (status-tier multipliers, 12-month window). The sourcing claim sits slightly at odds with openWorldHint=false but is not a direct contradiction.

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 core formula is front-loaded, but the body is a dense run-on that packs tier thresholds, creditTo routing, segs rules, and sourcing into few sentences with heavy parentheticals, making it hard to parse. Most content earns its place, yet structure and readability suffer.

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 9-parameter tool with an output schema, the description covers the earning rules, the tier thresholds, the segs input contract, and the partner-credit path well. Return values need not be explained given the output schema. Minor gaps remain around defaults/ordering that the schema mostly covers.

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 the baseline is 3, but the description adds meaning: it explains that 'sm' is Status Miles so far used only for tier progress, that status determines Business multipliers while Economy is unchanged, and that creditClass/creditStatus only matter with creditTo. These go beyond the enumerated schema text.

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?

Names the specific program and the two outputs it computes (Miles and Status Miles) and states the calculation basis (distance x booking-class rate, fixed Miles within Turkiye). This is unmistakably the Turkish Airlines calculator, distinct from the ~50 sibling airline calculators. No ambiguity about verb or resource.

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?

Tells the agent exactly what to supply ('Give segs: one entry per one-way flight, in order'), points to calculate_flight_distance as the sibling that produces the required distance, and notes it 'Takes no price.' It lacks explicit when-not guidance, but the precondition about segs and the distance handoff are clear.

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 tools Inspect

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

Need Help?