Skip to main content
Glama

Luxury Travel Tools by Global Lux Agency

Experience Pricing Calculator

experience-pricing-calculator
Read-onlyIdempotent

Prices a private or small-group experience from its costs. Takes fixed costs per departure, variable costs per guest and overhead, then returns the net price per guest that hits a target margin, the public (rack) price that still leaves that net after the agent or OTA commission (grossing up, not adding commission on top), the break-even group size, and a table of cost, price and profit for each group size. Web page: https://globalluxagency.com/tools/experience-pricing-calculator

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": {
      "fixedCostsPerDeparture": "<fixedCostsPerDeparture>",
      "variableCostsPerGuest": "<variableCostsPerGuest>"
    },
    "name": "experience-pricing-calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoCurrency of the amounts.GBP
maxGuestsNoLargest group size to model.
minGuestsNoSmallest group size to model.
pricingGuestsNoGroup size the suggested net price is based on.
netPriceOverrideNoYour own net price per guest. 0 = use the suggested price.
commissionPercentNoCommission the agent or OTA keeps, % of the public price (default 20% is a modelling choice; see sources for typical ranges).
targetMarginPercentNoTarget margin, % of the net price you receive (default 30% is a modelling choice).
overheadPerDepartureNoShare of business overheads allocated to each departure.
variableCostsPerGuestYesCosts paid for each guest (tickets, meals, tastings), in total per guest.
fixedCostsPerDepartureYesCosts paid once per departure whatever the group size (guide, vehicle, venue hire, permits), in total.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations, including the returned net price, rack price, break-even group size, and a per-group-size cost/price/profit table. It also clarifies a critical calculation nuance: commission is grossed up rather than added on top of the public price.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the tool's purpose and then lists the outputs in a logical sequence. Despite being a long sentence, every clause carries substantive pricing or return-value information, and there is no filler.

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

Completeness5/5

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

For a 10-parameter calculator with no output schema, the description is complete enough: the input schema fully documents parameters, while the description explains the key outputs and calculation behavior. An agent can understand what the tool computes and what it returns.

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 parameter meaning is already well documented. The description still adds useful conceptual semantics by tying fixed costs, variable costs, overhead, target margin, and commission into the pricing calculation, especially the grossing-up distinction for commission.

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?

States a specific verb and resource: it prices a private or small-group experience from its costs. This is clear and distinct enough to understand the tool's core function, but it does not explicitly differentiate itself from sibling pricing, commission, or budgeting calculators.

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 description: use it when pricing an experience from fixed and variable costs, overhead, margin, and commission. There is no explicit when-to-use guidance, exclusions, or named alternatives, so the agent must infer fit from the purpose.

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