Skip to main content
Glama
Sign In

cwsi.net Fare Classes & Mileage Calculators

by net.cwsi
OverviewDiscussionsAdmin

Air Europa Suma Miles Calculator

calculate_air_europa_miles
Read-onlyIdempotent

Air Europa Suma Miles for an Air Europa ticket, from the fare in euros (EUR: fare plus fuel surcharge, no taxes or fees, whole ticket): 5 Miles per EUR 1, plus 1 on flights to and from America (route AM) and 3 in Business (cabin J), plus a level bonus of 50% (Silver), 75% (Gold) or 100% (Platinum) of the base 5, rounded up. Premium Economy earns the Economy rate. Level Miles per flight are not published, so they are not calculated; Silver, Gold and Platinum need 18,000, 32,000 or 60,000 Level Miles, or 14, 26 or 50 flights, in 12 months (at least 4 on Air Europa). Uses cwsi.net's calculator and the airline's published rules. Give the price in EUR, not US dollars. Unofficial.

Input Schema

NameRequiredDescriptionDefault
cabinNoCabin. Y = Economy (Lite, Standard, Flex); W = Premium Economy (Standard, Flex); J = Business (+3 per €1). Business adds 3 Miles per €1. Premium Economy earns at the Economy rate.Y
priceNoFare paid (EUR, whole ticket) in EUR. In euros: the fare plus the fuel surcharge for the whole ticket, without taxes and fees. For another currency, enter the equivalent in euros. Required unless creditTo is given.
routeNoWhere the flight goes. EU = Spain and Europe (5 per €1); AM = America (6 per €1). Air Europa gives one rate for Spain and Europe and a higher one for America flights.EU
statusNoYour Suma level when you fly. BS = Suma (no bonus); SV = Silver (+50%); GD = Gold (+75%); PT = Platinum (+100%). The level bonus is a percentage of the base 5 Miles per €1.BS
creditToNoCredit the flights to a partner program instead of Air Europa's own: delta = Delta SkyMiles (creditStatus one of: SkyMiles Member, Silver Medallion, Gold Medallion, Platinum Medallion, Diamond Medallion); 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.
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. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already confirm a safe read-only, idempotent, non-destructive operation. The description adds substantial behavioral context: the exact calculation rules, rounding, that Level Miles are not published and therefore not calculated, the data source (cwsi.net), the unofficial status, and a currency warning. This goes well beyond what structured fields provide.

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?

The first sentence is long and dense, and the inclusion of Level Miles thresholds (18,000/32,000/60,000 or 14/26/50 flights) is tangential to calculating redeemable miles. Information is front-loaded, but the description carries unnecessary detail that dilutes focus.

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

Completeness3/5

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

For an 8-parameter tool with two distinct operating modes (own program vs partner crediting), the main description only covers the Air Europa Suma Miles mode and entirely omits the creditTo, creditClass, creditStatus, and creditFlights functionality. Although the schema documents those parameters, the description leaves an agent unaware of the tool's full capability.

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 eight parameters thoroughly. The description restates some rules (5 Miles per EUR, route/cabin bonuses, level bonuses) but adds no per-parameter meaning beyond the schema, particularly for the four creditTo-related parameters it ignores entirely.

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 the specific airline (Air Europa) and program (Suma Miles), clearly distinguishing it from the many sibling airline mileage calculators. An agent can tell immediately what this tool computes.

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?

The airline name implies the tool is for Air Europa tickets, but there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives among the sibling calculators. The description also fails to note when to use the partner credit mode versus the default mode.

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