Skip to main content
Glama

Luxury Travel Tools by Global Lux Agency

RevPAR calculator: ADR, occupancy, TRevPAR and GOPPAR

revpar-calculator
Read-onlyIdempotent

From rooms, nights in the period, room nights sold and rooms revenue, returns occupancy (sold ÷ available), ADR (rooms revenue ÷ sold) and RevPAR (rooms revenue ÷ available, = ADR × occupancy). Optional total revenue gives TRevPAR and the rooms share of revenue; optional gross operating profit gives GOPPAR and GOP margin (null when not supplied). With a target RevPAR, returns the ADR needed at a given occupancy (default: actual) and the occupancy needed at the current ADR. Rooms sold are capped at rooms available. Web page: https://globalluxagency.com/tools/revpar-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": {
      "rooms": "<rooms>",
      "nights": "<nights>",
      "roomNightsSold": "<roomNightsSold>",
      "roomsRevenue": "<roomsRevenue>"
    },
    "name": "revpar-calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomsYesRooms counted as available.
nightsYesNights (days) in the period, e.g. 30 or 365.
currencyNoCurrency of the amounts.GBP
roomsRevenueYesRooms revenue for the period.
targetRevparNoTarget RevPAR. 0 = no target.
totalRevenueNoTotal hotel revenue, all departments. 0 = not supplied.
roomNightsSoldYesRoom nights sold in the period.
grossOperatingProfitNoGross operating profit (USALI), can be negative. 0 = not supplied.
targetOccupancyPercentNoOccupancy, %, for the target ADR. 0 = use the actual occupancy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add behavioral context — and it does: rooms sold are capped at rooms available, GOPPAR and GOP margin are null when profit is not supplied, and the target-occupancy input falls back to actual occupancy. The clamping rule and null behavior are genuine details an agent could not infer from annotations.

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 a single dense paragraph, but it is front-loaded with the core formulas and every clause carries information about inputs or outputs. The trailing web-page URL is the only element that does not help an agent invoke the tool.

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 nine parameters and no output schema, the description must enumerate return values, and it does name every expected output including the conditional ones and their null case. It does not describe the response shape or how multiple results are packaged, which is the main remaining gap for a tool without an output schema.

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 carries per-field documentation and the baseline would be 3. The description adds cross-parameter semantics beyond that: which inputs drive which outputs (revenue + sold → ADR, total revenue → TRevPAR and rooms share, GOP → GOPPAR/margin) and the default behavior of targetOccupancyPercent. This maps parameters to results rather than restating field descriptions.

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?

The description names the specific inputs (rooms, nights, room nights sold, rooms revenue) and the exact metrics produced (occupancy, ADR, RevPAR, TRevPAR, GOPPAR), including the formulas used. That level of specificity separates it cleanly from sibling calculators such as hotel-upsell-revenue-calculator or hotel-overbooking-calculator without needing to reference them.

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?

It clearly signals which inputs are required versus optional and what each optional input unlocks ('Optional total revenue gives TRevPAR...'), which tells an agent when the tool's extended outputs are available. It stops short of explicit when-not-to-use guidance or naming alternative tools for adjacent questions.

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