Skip to main content
Glama

cwsi.net Fare Classes & Mileage Calculators

LOT Polish Airlines Miles & More Calculator

calculate_lot_polish_airlines_miles
Read-onlyIdempotent

Miles & More miles, Points, Qualifying Points and HON Circle Points for flights operated and ticketed by LOT Polish Airlines (ticket number 080), by booking class. Within one European country and between European countries: fixed miles by class; international: distance x class factor (25% to 200%) with a minimum per class. I, J, N and X earn nothing. Points and Qualifying Points per flight by cabin, continental or intercontinental (Economy 20/60, Premium Economy 20/80, Business 40/200; HON Circle Points in Business only). Algeria, Egypt, Libya, Morocco and Tunisia count as Europe; set tc to EU or AS for Turkey, Cyprus, Georgia, Armenia, Azerbaijan, Kazakhstan and Russia. LOT flights booked through a Lufthansa Group channel earn by fare instead (calculate_lufthansa_miles). Give segs: one entry per one-way flight, in order, with its great-circle miles (calculate_flight_distance gives them) and the ISO country codes of its two airports. Takes no price. Uses cwsi.net's calculator and the airline's published rules. Unofficial.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "segs": "<segs>"
    },
    "name": "calculate_lot_polish_airlines_miles"
  }
}

Input Schema

NameRequiredDescriptionDefault
hpNoHON Circle Points you have this year (optional). Only applies to some choices of the other fields; ignored otherwise.
qpNoQualifying Points you have this year (optional).
tcNoTurkey, Cyprus, the Caucasus, Kazakhstan and Russia count as. EU = Europe; AS = Asia (outside Europe). These countries lie on two continents and Miles &amp; More does not say which one it counts. Only applies to some choices of the other fields; ignored otherwise.EU
clsNoBooking class. C = C (Business 200%); D = D (Business 200%); F = F (Business 150%); Z = Z (Business 150%); P = P (Premium Economy 160%); A = A (Premium Economy 150%); R = R (Premium Economy 100%); Y = Y (Economy 150%); B = B (Economy 150%); M = M (Economy 100%); E = E (Economy 100%); H = H (Economy 100%); K = K (Economy 100%); Q = Q (Economy 100%); G = G (Economy 50%); S = S (Economy 50%); T = T (Economy 50%); V = V (Economy 50%); L = L (Economy 25%); O = O (Economy 25%); U = U (Economy 25%); W = W (Economy 25%); I = I (earns nothing); J = J (earns nothing); N = N (earns nothing); X = X (earns nothing). The letter on your ticket. Business C, D, F, Z; Premium Economy P, A, R; the rest Economy. I, J, N and X earn nothing.M
ptsNoPoints you have this year (optional). Used only for the progress toward the next tier.
segsYesThe flights, one way and in order, one entry per flight (1 to 8): fromCountry and toCountry, the ISO 3166 two-letter country codes of its two airports; miles, its great-circle distance in miles (1 to 12,500); optional from and to, the IATA codes of its two airports, which label the breakdown; some airlines also use them (Vladivostok, VVO, on JAL and ANA; the Madrid-Barcelona Air Shuttle, MAD-BCN, on Iberia; the long-haul tables named by city on SAS).
tripNoTrip. ow = One way; rt = Round trip. Round trip counts the same flights back the other way.ow
statusNoYour Miles &amp; More status. MM = Member (no status); FT = Frequent Traveller; SE = Senator; HC = HON Circle. Used for the progress toward the next tier. The bonus of up to 25% more miles for status holders is not published as a rule, so it is not added.MM
creditToNoCredit the flights to a partner program instead of LOT Polish Airlines'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 booking class is cls (or creditClass). The flights are segs (their miles), or creditFlights.
creditClassNoThe booking class letter for creditTo, when it differs from the class question. 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. Changed3 schema fields changed
    • addedInput schema / properties / creditClass
      Added value: +{
      +  "description": "The booking class letter for creditTo, when it differs from the class question. 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"
      +}
    • changedInput schema / properties / creditTo / description
      Previous value: -"Credit the flights to a partner program instead of LOT Polish Airlines'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."New value: +"Credit the flights to a partner program instead of LOT Polish Airlines'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 booking class is cls (or creditClass). The flights are segs (their miles), or creditFlights."
  2. Changed2 schema fields changed
    • 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 LOT Polish Airlines'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.",
      +  "enum": [
      +    "united",
      +    "aeroplan"
      +  ],
      +  "type": "string"
      +}
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: it discloses the data source ('cwsi.net's calculator and the airline's published rules'), that it is 'Unofficial', and that it 'Takes no price', which matters for a 12-parameter tool.

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

Conciseness3/5

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

Purpose is front-loaded, which is good, but the body is a dense run-on that intermixes earning rules, currency exclusions, geography exceptions, parameter instructions and source disclaimers across many parenthetical clauses. Much of the class-by-class earning detail duplicates what is already in the cls enum, so the size is partly redundant rather than purely additive.

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?

An output schema exists, so return values need not be explained, and the description covers what remains: the earning model, the rerouting sibling, the segs input shape, the creditTo partner programs, and the source for great-circle miles. For a 12-parameter tool it is complete enough to invoke correctly.

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 description coverage is 100%, so the baseline is 3, and the schema itself already documents most parameters. The description still adds meaning the schema does not fully convey, notably the rationale for tc (Algeria/Egypt/Libya/Morocco/Tunisia count as Europe; set EU or AS for the two-continent countries) and the requirement that segs be one entry per one-way flight in order with great-circle miles.

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?

States a specific verb and resource: computing Miles & More miles, Points, Qualifying Points and HON Circle Points for flights operated and ticketed by LOT (ticket 080), by booking class. It also distinguishes itself from the sibling calculate_lufthansa_miles and even names the shared prerequisite calculate_flight_distance, so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Explicit scope conditions ('operated and ticketed by LOT Polish Airlines (ticket number 080)'), an exclusion that reroutes the agent ('LOT flights booked through a Lufthansa Group channel earn by fare instead (calculate_lufthansa_miles)'), and a special-case note about tc for Turkey/Cyprus/etc. It also notes classes that earn nothing. Alternative paths are named, not implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources