Skip to main content
Glama

cwsi.net Fare Classes & Mileage Calculators

ITA Airways Miles & More Calculator

calculate_ita_airways_miles
Read-onlyIdempotent

Miles & More miles, Points, Qualifying Points and HON Circle Points for flights operated by ITA Airways (ITA joined Star Alliance on 1 April 2026; its Volare program ended and ITA flights earn in Miles & More), by booking class. Within one European country and between European countries: fixed miles by class (European Domestic, European Cross-Border); worldwide: distance x class factor (25% to 200%) with a minimum per class. A, F, I, O, R and X earn nothing; E, G and N (Premium Economy) are listed for worldwide flights only. 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. Miles & More says ITA miles go by ticket price or by booking class depending on how you book, and does not state which bookings earn by price; these are its booking-class rates. 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_ita_airways_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%); J = J (Business 200%); Z = Z (Business 150%); P = P (Business 100%); E = E (Premium Economy 150%); G = G (Premium Economy 150%); N = N (Premium Economy 100%); Y = Y (Economy 150%); B = B (Economy 150%); H = H (Economy 100%); M = M (Economy 100%); U = U (Economy 100%); Q = Q (Economy 50%); S = S (Economy 50%); V = V (Economy 50%); W = W (Economy 50%); K = K (Economy 25%); L = L (Economy 25%); T = T (Economy 25%); A = A (earns nothing); F = F (earns nothing); I = I (earns nothing); O = O (earns nothing); R = R (earns nothing); X = X (earns nothing). The letter on your ticket. Business C, D, J, Z, P; Premium Economy E, G, N; the rest Economy. A, F, I, O, R 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 50% 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 ITA Airways'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. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent, so the description is free to spend its words on real behavioral caveats and does: which classes earn nothing, which are Premium-Economy-only worldwide, the status bonus being deliberately not added because unpublished, the Miles & More price-vs-class ambiguity, the tc continent ambiguity, and that the source is unofficial (cwsi.net). This is exactly the beyond-annotation context an agent needs.

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 in the first clause, but the body is a single dense paragraph of semicolon-chained clauses mixing program history, earnings rules, geography exceptions and caveats. Some sentences (the segs structure, the A/F/I/O/R/X earn-nothing list) restate the schema, and the airline-history aside is lower value than the routing rules.

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?

For a 12-parameter tool with nested segs, an output schema and full schema coverage, the description covers the hard parts: segment shape, class outcomes, geography edge cases and the partner-program escape hatch. Gaps are minor, e.g. trip=rt behavior and status/points interplay are left entirely to the schema.

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 adds meaning the schema lacks: the North-Africa-counts-as-Europe rule for country classification, the fact that hp/qp/pts/status affect only tier progress, and that segs must be ordered one-way legs. It does not explain trip or the creditTo vs cls precedence in much depth, so it edges just above baseline rather than replacing 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?

States a specific resource (Miles & More miles, Points, Qualifying Points, HON Circle Points) for a specific airline (ITA Airways) and explains the program context (ITA joined Star Alliance, Volare ended) so it is unmistakable against the ~50 sibling airline calculators. Also names what is computed: fixed miles by class within Europe, distance x class factor worldwide.

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 invocation guidance: segs must be one entry per one-way flight in order with great-circle miles, and it explicitly routes to calculate_flight_distance for those miles. It also frames the creditTo partner-program alternative and states the tool takes no price. It never explicitly says to use a different sibling for a different airline, but the airline-specific framing makes that implicit.

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