cwsi.net Fare Classes & Mileage Calculators

Delta SkyMiles Calculator

calculate_delta_miles

Read-onlyIdempotent

Estimate what a Delta Air Lines 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

Name	Required	Description	Default
`card`	No	Paying with a Delta Amex card. none = No; BL = Blue; GO = Gold; PL = Platinum; RE = Reserve.	none
`fare`	No	Fare type. CR = Classic (or Refundable); EX = Extra; PB = Basic (Comfort, First, Premium Select, One); BA = Main Basic (Basic Economy). Delta Comfort, First, Premium Select and Delta One earn as Classic or Extra, whichever you bought. Their Basic fares earn as Basic.	CR
`price`	No	Ticket price in US dollars. Base fare plus carrier charges, without government taxes and fees (shown on your receipt). Required unless creditTo is given.
`status`	No	Your Medallion status. none = None; FO = Silver; GM = Gold; PM = Platinum; DM = Diamond.	none
`creditTo`	No	Credit the flights to a partner program instead of Delta Air Lines's own: flying-club = Flying Club (creditStatus one of: Red, Silver, Gold); 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. 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 Delta Air Lines's own: flying-club = Flying Club (creditStatus one of: Red, Silver, Gold); 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. 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": [
+    "flying-club",
+    "flying-blue"
+  ],
+  "type": "string"
+}

changedInput schema / properties / price / description

Previous value: -"Ticket price in US dollars. Base fare plus carrier charges, without government taxes and fees (shown on your receipt)."New value: +"Ticket price in US dollars. Base fare plus carrier charges, without government taxes and fees (shown on your receipt). Required unless creditTo is given."

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

Changed1 schema field changedOct 9, 2026

changedInput schema / properties / fare / description

Previous value: -"Fare type. CR = Classic (or Refundable); EX = Extra; PB = Basic (First, Premium Select, One); BA = Main Basic (Basic Economy). Delta Comfort, First, Premium Select and Delta One earn as Classic or Extra, whichever you bought."New value: +"Fare type. CR = Classic (or Refundable); EX = Extra; PB = Basic (Comfort, First, Premium Select, One); BA = Main Basic (Basic Economy). Delta Comfort, First, Premium Select and Delta One earn as Classic or Extra, whichever you bought. Their Basic fares earn as Basic."

Changed1 schema field changedOct 9, 2026
- addedInput schema / properties / price / maximum
```
Added value: +1000000
```
First observedOct 5, 2026

TDQS

A3.5/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, closed-world profile, so the bar is lower. The description still adds genuine behavioral context beyond that: it discloses the underlying source (cwsi.net's calculator plus the airline's published rules) and flags the result as 'Unofficial', which is an accuracy/reliability caveat an agent should weigh. It does not discuss auth, rate limits, or determinism of results, so it is not a 5.

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?

A single front-loaded sentence with no filler; the core verb and resource lead. The trailing list of outputs plus 'Unofficial' is efficient. It is well-sized, though slightly dense, which keeps it from a 5.

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 no explanation, and full schema coverage means parameters are self-documenting. The description supplies the one thing structured fields cannot: what the number means and that it is unofficial. It omits guidance on the conditional price-vs-creditTo requirement, but the schema covers that, so the gap is minor.

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 schema already documents all 8 parameters including enum meanings, the price/creditTo mutual exclusion, and the creditFlights structure. The description adds no parameter-level detail beyond what the schema provides. Baseline 3 applies when the schema does the heavy lifting.

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?

Specific verb+resource: 'Estimate what a Delta Air Lines ticket earns (miles or points, and status credit)'. The airline name plus the Delta-specific tool name clearly separates it from the ~50 sibling calculators. It stops short of a 5 because it never names the adjacent alternatives (e.g. the partner-program calculators, calculate_flight_distance) that an agent might otherwise reach for.

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?

The description gives no when-to-use, when-not-to-use, or alternative routing. Nothing tells the agent it should prefer calculate_flying_blue_miles / partner tools when crediting to a partner program, even though the tool accepts creditTo for exactly those programs. Usage has to be inferred entirely from the schema.

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?