Skip to main content
Glama

FactLot

Hotel operating metrics (USALI)

calc_hotel_metrics
Read-onlyIdempotent

Occupancy, ADR, RevPAR, TRevPAR, and a USALI-style profit ladder for a period: departmental profit, GOP and margin, GOPPAR, management fees, EBITDA, FF&E reserve, and NOI (EBITDA less replacement reserve). Deterministic: use this instead of doing the math yourself; cite formula calc.hotel_metrics@1 and the returned steps, and surface any warnings.

Input Schema

NameRequiredDescriptionDefault
roomsYesRooms in inventory (keys).
nightsYesNights in the period, e.g. 365 for a year or 30 for a month.
fb_revenueNoFood and beverage revenue, USD (USALI Food and Beverage department revenue).
rooms_soldYesRoom-nights occupied by paying guests in the period (USALI: rooms sold, excluding complimentary rooms).
room_revenueYesRooms revenue for the period, USD (USALI Rooms department revenue, net of taxes and allowances).
other_revenueNoOther operated departments plus miscellaneous income, USD (USALI Other Operated Departments and Miscellaneous Income).
ffe_reserve_rateNoFF&E replacement reserve as a share of total operating revenue, e.g. 0.04 (USALI Replacement Reserve, below EBITDA).
rooms_out_of_orderNoRoom-nights (rooms × nights, not rooms) taken off the market in the period, e.g. 20 rooms closed for a 30-night renovation = 600. Subtracted from rooms × nights to give rooms available. USALI (11th ed.) keeps short-term out-of-order rooms in rooms available; include only rooms formally removed from sale.
management_fee_rateNoBase management fee as a share of total operating revenue, e.g. 0.03 (USALI Management Fees).
management_fee_fixedNoFixed or incentive management fee for the period, USD, added to the percentage fee (USALI Management Fees).
departmental_expensesNoTotal departmental expenses, USD: rooms, F&B, and other operated departments (USALI Total Departmental Expenses).
non_operating_expensesNoProperty taxes, insurance, ground rent, and other non-operating expenses, USD (USALI Non-Operating Income and Expenses).
undistributed_expensesNoTotal undistributed operating expenses, USD: administrative and general, information and telecommunications, sales and marketing, property operation and maintenance, utilities (USALI Total Undistributed Operating Expenses).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context beyond that: the computation is deterministic, it returns intermediate steps, it can emit warnings, and results should be cited as calc.hotel_metrics@1 — all of which affect how an agent should present the output. It does not describe error behavior or input-validation failure modes.

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?

Two sentences: the first front-loads the full output inventory, the second states the operating directive (deterministic, prefer over manual math, cite the formula, surface warnings). No filler, no repetition of schema content, and the most decision-relevant information leads.

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 13-parameter, read-only calculator with no output schema, the description sufficiently enumerates what comes back (the full metric ladder including NOI) so an agent knows what to expect. It omits any note on output shape or how the 'steps' and 'warnings' are structured, which is a minor gap given there is no output schema to fall back on.

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 13 parameters carries a detailed USALI-anchored description, so the schema does the heavy lifting. The description adds only one implicit parameter clarification ('NOI = EBITDA less replacement reserve', which maps to ffe_reserve_rate) and otherwise does not restate or extend parameter meaning; 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 names the specific metrics produced (occupancy, ADR, RevPAR, TRevPAR, GOP, GOPPAR, EBITDA, NOI) and the resource domain (hotel operating metrics, USALI), which lets an agent distinguish it from the other calc_* siblings by subject matter. It stops short of explicitly contrasting itself with any named sibling, but the domain scope is unmistakable.

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?

It gives one clear usage directive — 'use this instead of doing the math yourself' — which tells the agent to prefer this tool over manual computation. It offers no guidance on when not to use it, what preconditions apply (e.g. data availability, period alignment), or how it relates to the many sibling calc_* tools beyond implicit domain separation.

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.