Skip to main content
Glama

Luxury Travel Tools by Global Lux Agency

Group trip cost splitter: yacht charter, villa and private jet

group-trip-cost-splitter
Read-onlyIdempotent

Divides one total between up to 12 parties: equally per person, equally per party, by person-nights, or by room weighting × nights (e.g. 1.5 for a master suite). Shares are whole cents (largest-remainder method) and add up exactly to the total. With amounts already paid, returns each party’s balance (paid − share) and settle-up transfers; anything unpaid is owed to the suppliers (to: null). Lists are comma-separated, one value per party, in the same order. The page supports several costs with a method each; this API takes one total. No sourced facts: all figures are the caller’s. Web page: https://globalluxagency.com/tools/group-trip-cost-splitter

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": {
      "total": "<total>",
      "partySizes": "<partySizes>"
    },
    "name": "group-trip-cost-splitter"
  }
}

Input Schema

NameRequiredDescriptionDefault
paidNoAmount each party has already paid, comma-separated (default 0).
totalYesThe shared cost to split, e.g. the charter fee.
methodNoHow to split: person (equally per person), party (equally per party), night (by person-nights), room (by room weighting × nights).person
nightsNoNights (or days) each party is present, comma-separated (default 7 for every party). Used by the night and room methods.
currencyNoCurrency of the amounts (labels only; nothing is converted).GBP
partySizesYesPeople in each party, comma-separated, e.g. "2,2,4" (1–50 each, up to 12 parties).
roomWeightsNoCabin or room weighting per party, comma-separated (default 1; e.g. 1.5 for a master suite). Used by the room method.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare it read-only, idempotent and non-destructive, and the description adds real behavioral detail beyond them: largest-remainder cent rounding with an exact-sum guarantee, the balance formula (paid − share), settle-up transfers, and the meaning of a null recipient (unpaid amounts owed to suppliers). That output semantics is essential given there is no output schema.

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?

Front-loaded with the core operation, then rounding, then outputs, then input conventions — a sensible order with little filler. The closing link and the page-vs-API note are slightly peripheral but still informative.

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 seven-parameter, no-output-schema, read-only calculation tool, the description covers inputs, method semantics, rounding behavior, and return contents. Nothing an agent needs in order to call it correctly and interpret the result is missing.

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 schema already documents every parameter including defaults and enums. The description still adds the operational constraint that all list inputs are comma-separated with one value per party in the same order, which is an alignment requirement the schema implies but does not state explicitly.

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 a specific verb and resource ("Divides one total between up to 12 parties") and enumerates the four split methods, which separates it from the sibling cost calculators that compute a single figure rather than apportioning a shared total.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for use — splitting a shared cost with optional already-paid amounts to derive balances and settle-up transfers — and explicitly bounds scope ("this API takes one total" versus the multi-cost web page). It does not explicitly name a sibling or a when-not condition, keeping it below a 5.

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