Skip to main content
Glama

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real context beyond them: rounding changes the commission the reseller actually keeps, and the default 15% is only a modelling example because real rates are negotiated. It does not describe the returned figures or their ordering, which is a notable omission for a calculator with 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?

Content is front-loaded with the core calculations and the opening sentence, while long, is dense with usable information. Each clause (markup variant, rounding effect, child pricing, default caveat) carries distinct value; the trailing URL is the only near-wasted element.

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 a read-only calculator with full schema coverage and no output schema, the description covers inputs, both conversion directions, rounding side effects, and child pricing. The main residual gap is that it never enumerates the outputs returned (net, retail, effective commission, child price), which an agent must infer.

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 meanings are already documented and the baseline is 3. The description goes further by explaining how priceEntered and model interact with the formulas and by flagging that ratePercent defaults are illustrative rather than authoritative, which is meaning the schema alone does not convey.

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 states a specific computation with explicit formulas (net = retail × (1 − commission), retail = net ÷ (1 − commission)), plus markup mode, rounding, and optional child pricing, so an agent knows exactly what the tool returns. It does not differentiate itself from a plausible sibling such as travel-agent-commission-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?

The scenario (reseller pricing, negotiated commission rates) is implied by the formulas and the note that defaults are examples, which is useful framing. There is no explicit when-to-use versus when-not guidance and no named alternative tool, leaving selection between this and the commission calculator to inference.

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