Skip to main content
Glama

cwsi.net Fare Classes & Mileage Calculators

by net.cwsi
OverviewDiscussionsAdmin

American AAdvantage Calculator

calculate_american_miles
Read-onlyIdempotent

Estimate what a American 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 AAdvantage card. none = No; MU = MileUp (+2 per $1); PS = Platinum Select (+2 per $1); GB = Globe (+3 per $1); EX = Executive (+4 per $1).none
fareNoFare type. 1 = Standard (Main Cabin and above); 0 = Basic Economy.1
priceNoTicket price in US dollars. Base fare plus carrier-imposed fees, without government taxes. Required unless creditTo is given.
statusNoYour AAdvantage status. none = None; GL = Gold (+40%); PL = Platinum (+60%); PP = Platinum Pro (+80%); EP = Executive Platinum (+120%).none
creditToNoCredit the flights to a partner program instead of American Airlines's own: alaska = Atmos Rewards (creditStatus one of: Atmos Rewards member, Atmos Silver, Atmos Gold, Atmos Platinum, Atmos Titanium). 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 American Airlines's own: alaska = Atmos Rewards (creditStatus one of: Atmos Rewards member, Atmos Silver, Atmos Gold, Atmos Platinum, Atmos Titanium). 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": [
+    "alaska"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / price / description
      Previous value: -"Ticket price in US dollars. Base fare plus carrier-imposed fees, without government taxes."New value: +"Ticket price in US dollars. Base fare plus carrier-imposed fees, without government taxes. 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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two genuinely useful facts beyond that: results are estimates, not exact, and they come from cwsi.net's calculator plus published airline rules ("Unofficial"). It says nothing about determinism or edge cases, so this is solid but not rich.

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 sentence with no filler, front-loading the purpose and appending the important "Unofficial" caveat. Minor awkwardness in phrasing ("what a American Airlines ticket earns") but nothing wasteful.

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 100% parameter coverage plus read-only annotations mean the structured fields cover most needs. The remaining gap is cross-tool routing (creditTo to Alaska vs. calculate_alaska_miles, and the dependency on calculate_flight_distance for creditFlights.miles, which is only mentioned in the schema).

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 the enum values, card multipliers, status bonuses and creditTo mechanics are all documented inline. The description adds no parameter-level meaning; it only hints that outputs may be miles, points or status credit. Baseline 3 is appropriate when the schema carries the burden.

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 and resource: "Estimate what a American Airlines ticket earns (miles or points, and status credit where it applies)". An agent can tell this is the AAdvantage earning calculator. It does not distinguish itself from siblings, though the airline-specific name plus the ~50 parallel calculators makes that differentiation largely self-evident.

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

Usage Guidelines3/5

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

Scope is implied — it covers American Airlines tickets and status credit "where it applies" — but there is no explicit when-to-use/when-not statement. Notably, the tool supports crediting to Alaska (creditTo) which overlaps with the sibling calculate_alaska_miles, and the description never routes the agent between the two; that guidance lives only in 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 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