cwsi.net Fare Classes & Mileage Calculators

Finnair Avios and Tier Points Calculator

calculate_finnair_avios

Read-onlyIdempotent

Finnair Plus Avios and tier points for a Finnair ticket. Both = (fare in EUR: the base fare plus any airline surcharge for the whole ticket, without taxes; plus travel extras on Finnair flights) x tier factor (Basic 6, Silver 7, Gold 8, Platinum 9, Platinum Lumo 10), rounded down. Set flt to CS for a Finnair codeshare flight (AY2501-AY7000) booked from 3 June 2025, where extras earn nothing. Progress toward Silver (15,000), Gold (45,000), Platinum (80,000) and Platinum Lumo (300,000) tier points; tp is the tier points so far. Uses cwsi.net's calculator and the airline's published rules. Give the price in EUR, not US dollars. Unofficial.

Input Schema

Name	Required	Description	Default
`tp`	No	Tier points you have so far (optional). Used only for the progress toward the next tier.
`flt`	No	Flight. AY = Finnair flight (AY0001-AY2000, AY7001-AY7500); CS = Codeshare flight (AY2501-AY7000, booked from 3 June 2025). The flight number on your ticket. Codeshare flights booked before 3 June 2025 earn by distance and are not covered here.	AY
`price`	No	Fare paid (EUR, whole ticket) in EUR. In euros: the base fare plus any airline surcharge ("Extra fee" in the price breakdown) for the whole ticket, without taxes and airport charges. Finnair converts a fare paid in another currency to euros itself. Required unless creditTo is given.
`extras`	No	Travel extras (EUR, optional). The total price of travel extras bought for Finnair flights (for example bags or seats). They earn at the same rate as the fare. Only applies to some choices of the other fields; ignored otherwise.
`status`	No	Your Finnair Plus tier when you fly. BS = Basic (6 per €1); SV = Silver (7 per €1); GD = Gold (8 per €1); PT = Platinum (9 per €1); LU = Platinum Lumo (10 per €1).	BS
`creditTo`	No	Credit the flights to a partner program instead of Finnair'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); 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. Give the flights as creditFlights (one entry per flight with its great-circle miles). No price is needed with creditTo.
`creditClass`	No	The booking class letter on the ticket, for creditTo (required with creditTo). 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.

Changed6 schema fields changedOct 13, 2026

addedInput schema / properties / creditClass

Added value: +{
+  "description": "The booking class letter on the ticket, for creditTo (required with creditTo). 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 Finnair'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); 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. Give the flights as creditFlights (one entry per flight with its great-circle miles). No price is needed with creditTo.",
+  "enum": [
+    "american",
+    "alaska",
+    "ba-club"
+  ],
+  "type": "string"
+}

changedInput schema / properties / price / description

Previous value: -"Fare paid (EUR, whole ticket) in EUR. In euros: the base fare plus any airline surcharge (\"Extra fee\" in the price breakdown) for the whole ticket, without taxes and airport charges. Finnair converts a fare paid in another currency to euros itself."New value: +"Fare paid (EUR, whole ticket) in EUR. In euros: the base fare plus any airline surcharge (\"Extra fee\" in the price breakdown) for the whole ticket, without taxes and airport charges. Finnair converts a fare paid in another currency to euros itself. Required unless creditTo is given."

removedInput schema / required
```
Removed value: -[
-  "price"
-]
```

AddedOct 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare the safe read-only/idempotent profile, so the bar is lower, and the description adds real behavioral context: the exact earning formula, tier factors, the rule that extras earn nothing on codeshare flights, tier-point thresholds, and the 'Unofficial' status plus cwsi.net data source. It does not contradict the annotations.

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

Conciseness4/5

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

The purpose and formula are front-loaded, and each sentence carries computation rules or constraints rather than filler. It is dense and somewhat run-on, and repeats tier-factor values already in the schema, but it is appropriately sized for a rule-heavy calculator.

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 explained, and the description covers the earning rules, codeshare/program branches, currency constraint, and source disclaimers. Coverage is complete enough for an agent to invoke the tool correctly across its branches.

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 coverage is 100% and the schema descriptions are themselves very detailed (price, extras, status, creditTo all fully documented). The description restates much of this, including the tier-factor mapping already present in the status enum. It adds the combined price+extras formula linking parameters, which earns it above a bare baseline, but most content duplicates the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource: Avios and tier points earned for a Finnair ticket, computed from fare x tier factor. An agent can immediately tell this is the Finnair-specific earnings calculator. It does not explicitly name sibling tools, but the airline scope in name/title makes the distinction obvious.

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 concrete usage conditions: set flt=CS for codeshare flights booked from 3 June 2025, leave creditTo out for Finnair's own program, and 'Give the price in EUR, not US dollars.' It also routes partner-program crediting through creditTo. It stops short of explicitly contrasting with the sibling calculate_*_miles tools, so not a 5.

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?