Skip to main content
Glama

Luxury Travel Tools by Global Lux Agency

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.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the burden is lighter, and the description still adds real value: it is stateless ('holds no award charts, fares or room rates'), warns that defaults are illustrative, states the Avios default target with an explicit confidence caveat ('opinion, low confidence'), and explains the tie-breaking/decision rule (highest net saving, else pay cash). It omits edge-case behaviour such as rounding and what happens when all options are zeroed out.

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?

Roughly five dense sentences with no filler, and each carries content: data ownership, formula, decision rule, marginalValue, default target, link. It is slightly back-loaded — the first sentence is a disclaimer rather than the purpose — but nothing is wasted.

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 compensates well by defining the computed outputs (value per point in hundredths of the currency, net saving, best option, marginalValue). Gaps are minor: no statement of return shape/structure and no mention of degenerate inputs, but an agent can call and interpret this correctly.

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 coverage is 100%, so baseline is 3; the description does add meaning by showing how the parameters combine (why earnOnCash is an opportunity cost, how option cash and points pair up, what targetValue does) and by documenting the target-default rule. It does not add per-parameter syntax beyond the schema, so this stays at the high-coverage baseline.

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 pins down the exact quantity computed — value per point = 100 × (cash price − cash paid on the award) ÷ (points used + points the cash booking would earn) — plus net saving against a target, so the operation is unambiguous. However, it never states the purpose in a plain sentence ('this tool calculates pence-per-point value for a redemption'), leaving that to the title, and it does not distinguish itself from the many other *-calculator siblings.

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?

Use is implied by the formula and by the note that the caller supplies all prices and points because the tool holds no award charts. There is no explicit when-to-use/when-not, no statement of prerequisites (e.g. same flight/cabin comparison is only implied inside the cashPrice schema), and no routing to alternatives such as the direct-booking-vs-ota or upgrade calculators.

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