Skip to main content
Glama

Avios value calculator: pence per point for any redemption

avios-value-calculator
Read-onlyIdempotent

All prices and points are the caller’s own: the tool holds no award charts, fares or room rates, and the defaults are an illustrative example. Value per point = 100 × (cash price − cash paid on the award) ÷ (points used + points the cash booking would earn), in hundredths of the currency. With a target value, net saving = cash saved − points given up × target ÷ 100, and the best option is the highest net saving (or paying cash if none is positive). marginalValue compares each option with the option using fewer points. For Avios with no targetValue given, the target defaults to a published 1p ball-park (opinion, low confidence). Web page: https://globalluxagency.com/tools/avios-value-calculator

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "avios-value-calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoCurrency of all amounts (no conversion). Values per point are in hundredths of it (pence for GBP, cents for EUR/USD).GBP
cashPriceNoCash price of the same booking (same flight and cabin, or room and dates).
programmeNoavios, virgin-points, hotel or other. Labels the result; for avios the default target is a published ball-park value.avios
earnOnCashNoPoints the cash booking would earn (opportunity cost). 0 to ignore.
option1CashNoOption 1: cash paid with the points (taxes, fees, carrier charges, or the money part of points + money).
option2CashNoOption 2: cash paid with the points (taxes, fees, carrier charges, or the money part of points + money).
option3CashNoOption 3: cash paid with the points (taxes, fees, carrier charges, or the money part of points + money).
targetValueNoYour target value per point in hundredths of the currency (e.g. pence). 0 = no target. Omitted: 1 for avios (a published ball-park), none otherwise.
option1PointsNoOption 1 (“All points”): points used. 0 leaves the option out.
option2PointsNoOption 2 (“Points + money”): points used. 0 leaves the option out.
option3PointsNoOption 3 (“Another mix”): points used. 0 leaves the option out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description still adds real value by disclosing that the tool holds no award charts, fares or room rates and that all defaults are an illustrative example the caller must replace. It also discloses the low-confidence published 1p default target for Avios and how marginalValue is compared. These are behavioural facts not present in the annotations or schema constraints.

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 lead sentence front-loads the most important caveat (caller-supplied prices and points, defaults are examples), followed by the formula and the output rules. It is dense but each sentence carries meaning; only the trailing web link feels like filler for an agent caller.

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 11 optional parameters and no output schema, the description does the necessary work by explaining what the returned figures mean: value per point in hundredths, net saving against a target, marginalValue relative to the lower-points option, and the best-option selection rule. A little more on how inactive options (0 points) are treated in marginalValue would make it fully complete.

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 a 3 is the baseline; the description earns more by tying parameters into one formula, showing that points a cash booking would earn enter the denominator as opportunity cost and that the target value drives the net-saving comparison. It also clarifies the omitted-target default behaviour per programme, which is a semantic rule the schema only partially hints at.

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?

The description states a specific resource and computation: value per point = 100 × (cash price − cash paid on award) ÷ (points used + points earned), in hundredths of the currency. That is unmistakably a points-redemption valuation calculator rather than a cost splitter or upgrade check. It does not explicitly name a sibling it is not, so it falls short of a 5.

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?

Usage is implied by the formula and by notes such as the cash price needing to be 'the same flight and cabin' and that paying cash wins when no option has positive net saving. However, there is no explicit statement of when to pick this tool over the many sibling calculators, nor any stated preconditions beyond input interpretation.

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