cwsi.net Fare Classes & Mileage Calculators

Air India Maharaja Club Calculator

calculate_air_india_points

Read-onlyIdempotent

Air India Maharaja Club Maharaja Points and Tier Points for an Air India or Air India Express (carrier IX) ticket, from the fare in Indian rupees (INR): Air India counts the base fare plus the fuel surcharge (YQ), Air India Express the base fare only, without taxes and fees. Maharaja Points = fare / 100 x 6 (Red), 8 (Silver), 9 (Gold) or 10 (Platinum), rounded down, plus 2 per INR 100 when booked directly on the Air India website or app (direct YES, Air India only); Tier Points = 6 per INR 100 at every tier. Air India converts a fare in another currency itself and does not publish the rate, so give the INR amount. Progress toward Silver (15,000), Gold (30,000) and Platinum (45,000) Tier Points in 365 days; tp is the Tier Points so far. Uses cwsi.net's calculator and the airline's published rules. Give the price in INR, not US dollars. Unofficial.

Input Schema

Name	Required	Description	Default
`tp`	No	Tier Points you have so far (optional). Tier Points from the last 365 days. Used only for the progress toward the next tier.
`price`	No	Fare paid (INR, whole ticket) in INR. In Indian rupees: the base fare plus the fuel surcharge (YQ) for Air India, or the base fare alone for Air India Express, without taxes and fees. Air India converts a fare paid in another currency itself. Required unless creditTo is given.
`direct`	No	Booked directly on the Air India website or app?. NO = No (travel agent or other); YES = Yes (+2 per INR 100). Direct bookings earn 2 bonus Maharaja Points per INR 100 on Air India flights. The bonus does not add Tier Points. Only applies to some choices of the other fields; ignored otherwise.	NO
`status`	No	Your Maharaja Club tier when you fly. RD = Red (6 per INR 100); SV = Silver (8 per INR 100); GD = Gold (9 per INR 100); PT = Platinum (10 per INR 100).	RD
`carrier`	No	Airline. AI = Air India (base fare plus YQ); IX = Air India Express (base fare only). Air India counts the base fare plus the fuel surcharge (YQ). Air India Express counts the base fare only.	AI
`creditTo`	No	Credit the flights to a partner program instead of Air India'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 programs follow the airline in carrier (AI: united, aeroplan; IX: none). 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 Air India'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 programs follow the airline in carrier (AI: united, aeroplan; IX: none). 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": [
+    "united",
+    "aeroplan"
+  ],
+  "type": "string"
+}

changedInput schema / properties / price / description

Previous value: -"Fare paid (INR, whole ticket) in INR. In Indian rupees: the base fare plus the fuel surcharge (YQ) for Air India, or the base fare alone for Air India Express, without taxes and fees. Air India converts a fare paid in another currency itself."New value: +"Fare paid (INR, whole ticket) in INR. In Indian rupees: the base fare plus the fuel surcharge (YQ) for Air India, or the base fare alone for Air India Express, without taxes and fees. Air India converts a fare paid in another currency itself. Required unless creditTo is given."

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

AddedOct 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly/idempotent/non-destructive), yet the description adds substantial operational context: rounding down, the unstated FX conversion behavior, the direct-booking bonus that adds Maharaja Points but not Tier Points, tier thresholds (15,000/30,000/45,000 over 365 days), and the 'unofficial, uses cwsi.net' provenance caveat.

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 core formula and the INR instruction are front-loaded, and every clause carries rule content rather than filler. It is a dense single paragraph, however, and the 'give the INR amount, not US dollars' instruction is effectively repeated at the end, which is mild redundancy.

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

Completeness5/5

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

For a 9-parameter calculator with an output schema (so return values need not be explained), the description covers the carrier/tier/direct math, the creditTo partner branch, and the currency constraint, plus provenance. Nothing needed to call it correctly is missing.

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 goes beyond field definitions by explaining how parameters interact: fare/100 x tier multiplier, +2 per INR 100 only when direct=YES on Air India, carrier AI counting base fare plus YQ versus IX counting base fare only. This formula-level context is not restated from 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?

Names the specific output (Maharaja Points and Tier Points) for a specific carrier set (Air India / Air India Express carrier IX), with the exact input basis (fare in INR). Against ~50 sibling calculators that differ only by airline, the carrier-specific scope makes it unmistakable which one to pick.

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?

Gives concrete routing rules: give the price in INR rather than USD because Air India converts foreign currency itself, and 'leave creditTo out for the airline's own program' while describing the partner-program path. It also points to calculate_flight_distance as the source of creditFlights miles. It stops short of naming an explicit alternative tool for partner crediting, so not a full 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?