Skip to main content
Glama

Luxury Travel Tools by Global Lux Agency

Private Jet vs First Class Calculator: Cost per Person

private-jet-vs-first-class-calculator
Read-onlyIdempotent

All prices and times are the caller’s own: the tool holds no fares or charter rates, and the defaults are an illustrative example, not quotes. The jet cost (quote + fees + extras) is shared equally; first class is fare + taxes per person, plus group extras. Break-even = ceil((jet total − first-class extras) ÷ (fare + taxes)). Times are per one-way journey and doubled for a return. Optional hourlyValue values each traveller’s hour saved. Web page: https://globalluxagency.com/tools/private-jet-vs-first-class-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": "private-jet-vs-first-class-calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
jetFeesNoJet fees not in the quote: taxes, positioning, landing, de-icing.
currencyNoCurrency of all amounts (no conversion).GBP
jetQuoteNoPrivate jet charter quote for the whole aircraft and the whole trip.
jetSeatsNoPassenger seats on the aircraft quoted.
tripTypeNooneway or return. Return doubles the door-to-door times; prices are for the whole trip either way.return
firstFareNoFirst-class fare per person for the whole trip.
jetExtrasNoJet extras for the group: transfers, VIP terminal, catering, pets.
firstTaxesNoFirst-class taxes and charges per person, if not in the fare.
travellersNoNumber of travellers.
firstExtrasNoFirst-class extras for the group: transfers, lounge, excess baggage, pets.
hourlyValueNoOptional value of each traveller’s time per hour; 0 leaves time out of the cost comparison.
jetAfterMinutesNoJet: time after landing. Minutes, one way.
jetBeforeMinutesNoJet: time at the airport before departure. Minutes, one way.
jetFlightMinutesNoJet: flight time. Minutes, one way.
firstAfterMinutesNoFirst class: time after landing (immigration, baggage). Minutes, one way.
firstBeforeMinutesNoFirst class: time at the airport before departure. Minutes, one way.
firstFlightMinutesNoFirst class: flight time including any connection. Minutes, one way.

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 readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds behavior beyond that: it explicitly disclaims any internal fare data, warns defaults are illustrative rather than quotes, and explains the allocation rules (jet cost shared equally, first class per person) and that times are one-way and doubled for returns.

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?

It is short and front-loads the most decision-relevant caveat (no real quotes, defaults are illustrative) before the cost and break-even rules. The compact math notation is efficient, though the break-even formula is dense and a single-sentence caveat plus formula plus URL reads as one long block rather than cleanly separated points.

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 17 optional parameters at full schema coverage and no output schema, the description carries the burden of explaining results, and it does give the break-even rule and the cost composition. It stops short of describing the full result set (e.g., whether per-person jet cost, savings, or time-adjusted totals are returned), which would fully close the no-output-schema gap.

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 genuinely adds semantics: it defines the jet total as quote + fees + extras shared across seats, the first-class total as fare + taxes per person plus group extras, and explains that hourlyValue values each traveller's hour saved, with 0 excluding time. It does not, however, spell out how travellers vs jetSeats interact in the per-person division.

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 names the exact comparison ('Private Jet vs First Class', per-person cost) and states the computation model: jet cost shared equally, first class fare + taxes per person plus group extras, and a break-even formula. An agent can tell this is a break-even cost-per-person calculator, though it never explicitly contrasts itself with sibling calculators like yacht-charter-cost-calculator beyond the subject matter.

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?

It establishes an important usage precondition — 'the tool holds no fares or charter rates, and the defaults are an illustrative example, not quotes' — so the caller knows to supply real prices. But there is no explicit when-to-use/when-not guidance and no named alternative tool for related comparisons; usage is only implied by the input-sourcing note.

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