cwsi.net Fare Classes & Mileage Calculators

Virgin Atlantic Flying Club Points Calculator

calculate_virgin_atlantic_points

Read-onlyIdempotent

Virgin Atlantic Flying Club Virgin Points and Tier Points for Virgin Atlantic flights. Virgin Points = distance x booking-class % (J, C, D 500; I, Z 300; W, S 250; H, K 175; V, Y, B, R 150; L, U, M 100; Q, X, N, O 50; T 25) x tier (Red 1, Silver 1.3, Gold 1.6), rounded per flight; Tier Points are fixed per flight by class (25 to 200). The reward-only classes G, P and A, and E (no published rate), are not offered. Progress toward Silver (400) and Gold (1,000) Tier Points; tp is the Tier Points 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
`tp`	No	Tier Points you have so far (optional). Used only for the progress toward Silver and Gold.
`cls`	No	Booking class. JCD = J, C, D (Upper Class, 500%, 200 Tier Points); I = I (Upper Class, 300%, 200 Tier Points); Z = Z (Upper Class, 300%, 100 Tier Points); WS = W, S (Premium, 250%, 100 Tier Points); HK = H, K (Premium, 175%, 50 Tier Points); V = V (Economy Delight, 150%, 50 Tier Points); YBR = Y, B, R (Economy Classic, 150%, 50 Tier Points); LUM = L, U, M (Economy Classic, 100%, 50 Tier Points); QXNO = Q, X, N, O (Economy Classic, 50%, 25 Tier Points); T = T (Economy Light, 25%, 25 Tier Points). The letter on your ticket. The percentage is of the distance flown. Reward-only classes (G, P, A) and E are not listed.	YBR
`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 Flying Club tier. R = Red; S = Silver (+30% Virgin Points); G = Gold (+60% Virgin Points).	R
`creditTo`	No	Credit the flights to a partner program instead of Virgin Atlantic's own: delta = Delta SkyMiles (creditStatus one of: SkyMiles Member, Silver Medallion, Gold Medallion, Platinum Medallion, Diamond Medallion); 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. 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 Virgin Atlantic's own: delta = Delta SkyMiles (creditStatus one of: SkyMiles Member, Silver Medallion, Gold Medallion, Platinum Medallion, Diamond Medallion); 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. The booking class is cls (or creditClass). The flights are segs (their miles), or creditFlights.",
+  "enum": [
+    "delta",
+    "flying-blue"
+  ],
+  "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 cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description adds useful context beyond that: it discloses the tool is 'Unofficial', that it relies on cwsi.net's calculator and published airline rules, and that reward-only classes (G, P, A, E) are not offered.

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?

It is front-loaded with the purpose and core formula, but the detailed class-percentage and tier-multiplier lists duplicate what the enum schema already documents, making it longer than needed for an agent that can read the schema.

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?

Given an output schema exists, return values needn't be explained. The description covers the calculation logic, segs requirement, excluded classes, and the partner-credit alternative, leaving little ambiguity for a complex 9-parameter tool.

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. The description goes further by pointing the agent to calculate_flight_distance for the miles value and clarifying the segs structure (one entry per one-way flight, in order, ISO country codes), adding cross-tool guidance beyond 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?

The description names the specific resource (Virgin Atlantic Flying Club Virgin Points and Tier Points) and verb (calculate), immediately distinguishing it from the ~50 sibling airline calculators by naming the program and the exact outputs (Virgin Points and Tier Points).

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 clearly states the scope ('for Virgin Atlantic flights'), what the tool takes ('Takes no price'), and how to supply inputs ('Give segs: one entry per one-way flight, in order...'). It doesn't contrast against a non-airline alternative, but for an airline-specific tool the context is 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?