Skip to main content
Glama

cwsi.net Fare Classes & Mileage Calculators

by net.cwsi
OverviewDiscussionsAdmin

Alaska Atmos Rewards Calculator

calculate_alaska_miles
Read-onlyIdempotent

Estimate what a Alaska Airlines ticket earns (miles or points, and status credit where it applies), using cwsi.net's calculator and the airline's published rules. Unofficial.

Input Schema

NameRequiredDescriptionDefault
cardNoPaying with an Atmos Rewards card. none = No; AS = Ascent (+3 per $1); SU = Summit (+3 per $1); BU = Business (+3 per $1).none
fareNoFare. 200 = First, full fare (J); 175 = First (C); 150a = First, discount (D, I); 150b = Main, full fare (Y, B); 125 = Main (H, K); 100 = Main, discount (M, L, V, S, N, Q, O, G); 0 = Saver (X). Only applies to some choices of the other fields; ignored otherwise.100
kindNoFare type. paid = Paid fare (Main, Premium, First); basic = Basic or Saver (earns 0). Only applies to some choices of the other fields; ignored otherwise.paid
segsNoSegments. Each flight (segment) earns 500 points. Only applies to some choices of the other fields; ignored otherwise.
whenNoWhen do you fly?. 2026 = Through Dec 31, 2026; 2027 = From Jan 1, 2027. Members choose a method from Oct 1, 2026; it applies to flights from Jan 1, 2027.2026
milesNoMiles flown. The flight distance in miles. Only applies to some choices of the other fields; ignored otherwise.
priceNoPrice paid (before taxes and fees) in US dollars. Needed for your card, or for the price method from 2027. Required unless creditTo is given.
legacyNoSaver booked early or flown soon. 1 = Yes (30%); 0 = No (earns 0). Saver earns 30% when booked before Jun 11, 2026, or flown through Jul 31, 2026. Otherwise it earns 0. Only applies to some choices of the other fields; ignored otherwise.0
methodNoYour earning method. dist = Distance (1 per mile); price = Price paid (5 per $1); seg = Segments (500 per segment). Only applies to some choices of the other fields; ignored otherwise.dist
statusNoYour Atmos status. none = Member (No status); SV = Silver (+25%); GD = Gold (+50%); PT = Platinum (+100%); TT = Titanium (+150%).none
creditToNoCredit the flights to a partner program instead of Alaska Airlines's own: american = American AAdvantage (creditStatus one of: AAdvantage member, AAdvantage Gold, AAdvantage Platinum, AAdvantage Platinum Pro, AAdvantage Executive Platinum); 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.
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. Changed6 schema fields changed
    • 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 Alaska Airlines's own: american = American AAdvantage (creditStatus one of: AAdvantage member, AAdvantage Gold, AAdvantage Platinum, AAdvantage Platinum Pro, AAdvantage Executive Platinum); 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",
+    "ba-club"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / price / description
      Previous value: -"Price paid (before taxes and fees) in US dollars. Needed for your card, or for the price method from 2027."New value: +"Price paid (before taxes and fees) in US dollars. Needed for your card, or for the price method from 2027. Required unless creditTo is given."
    • removedInput schema / required
      Removed value: -[
-  "price"
-]
  2. Changed1 schema field changed
    • addedInput schema / properties / price / maximum
      Added value: +1000000
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered. The description usefully adds that it is an 'Estimate', that it is 'Unofficial', and that results are derived from cwsi.net's calculator plus the airline's published rules — signalling approximation and possible staleness, which the annotations do not convey.

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?

Two compact sentences, front-loaded with the primary estimate action and closing with the sourcing/provenance caveat. No padding or redundancy, though it is arguably too terse for a 14-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. However, for a tool with 14 interacting parameters and a major 2026/2027 earning-method regime change, the description gives no orientation to those complexities, leaving the agent fully dependent on the schema to understand the two distinct calculation regimes.

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% and each of the 14 parameters carries a detailed description (enum semantics, defaults, applicability notes), so the schema does the heavy lifting. The description adds no parameter-level meaning beyond that, making the baseline of 3 appropriate.

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?

States a specific verb ('Estimate') and resource ('what an Alaska Airlines ticket earns — miles or points, and status credit'), which is immediately distinguishable from the per-airline siblings by the named carrier. It stops short of explicitly contrasting itself with adjacent tools like calculate_flight_distance or the partner calculators, but the core purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not guidance, no prerequisites, and no mention of alternatives. This matters because the schema exposes a creditTo path that overlaps with sibling tools (calculate_american_miles, calculate_british_airways_avios), and the description never tells the agent when to prefer one over the other.

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