Skip to main content
Glama

Luxury Travel Tools by Global Lux Agency

Net Rate Sheet Generator

net-rate-sheet-generator
Read-onlyIdempotent

Works out the net rate from a retail price (net = retail × (1 − commission)) or the retail price from a net rate (retail = net ÷ (1 − commission)), or the same with a markup on net, then rounds the worked-out price and reports the commission the reseller really keeps after rounding. Optionally prices a child at a % of the adult price. Commission rates are negotiated; the defaults are examples. Web page: https://globalluxagency.com/tools/net-rate-sheet-generator

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": {
      "price": "<price>"
    },
    "name": "net-rate-sheet-generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNocommission = % of the retail price; markup = % added to the net price.commission
priceYesThe price you set, per person or per group, in the terms given by priceEntered.
roundToNoRound the worked-out price to this step (0 = to 2 decimal places).1
currencyNoCurrency of the price.GBP
ratePercentNoCommission or markup %. Commission is capped at 95%. Default 15% is a modelling choice (midpoint of the typical retail travel agent range).
priceEnteredNoretail = price is the public (rack) price, work out the net; net = price is your net, work out the retail.retail
childRatePercentNoChild price as a % of the adult price. 0 = none.
roundingDirectionNoRounding direction.nearest

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 declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value: it discloses that the worked-out price is rounded and that the reported commission is the amount actually kept after rounding, and it warns that default rates are illustrative rather than authoritative. It does not describe result shape or the interaction between roundingDirection and roundTo.

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 core formulas are front-loaded in the first clause, and the follow-on points (rounding, kept commission, child pricing, default caveat) are compact. The trailing web-page URL is the only sentence that does not help an agent invoke the tool. Dense but efficient.

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?

For an 8-parameter, no-output-schema calculator the description covers the computation, the rounding and the reported commission, which is what an agent needs to call it correctly. Missing only output-shape detail and tie-breaking between rounding options. The read-only safety profile is already covered by annotations.

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 description coverage is 100% and each of the 8 parameters already carries an enum or explanatory text, so the schema does the heavy lifting. The description reinforces the priceEntered and model semantics through the formulas but adds no syntax, unit, or edge-case detail the schema lacks. Baseline 3 applies.

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 gives the exact arithmetic it performs (net = retail × (1 − commission), retail = net ÷ (1 − commission)), the markup variant, rounding, and optional child pricing. That is a specific verb-plus-resource statement far beyond the tautological title. It does not name or distinguish any sibling calculator, so it stops 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 only implied by the formulas: an agent can infer it is for converting between retail and net prices. There is no explicit when-to-use versus alternatives guidance, even though siblings like travel-agent-commission-calculator plausibly overlap. The one genuinely directive sentence is the caution that commission rates are negotiated and defaults are examples.

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