Skip to main content
Glama

Motel Loans: hotel loan sizer and franchise costs

Size a hotel or motel loan

size_hotel_loan
Read-onlyIdempotent

Runs the motel.loans hotel loan sizer on your numbers: RevPAR, rooms and total revenue, each expense line, NOI, annual debt service, DSCR, the largest loan the cash flow supports at the lender's minimum DSCR, the loan-to-price cap, which one binds, cap rate, price per key and breakeven occupancy. Pick a brand to fill franchise fees from its FDD and a program (SBA 7(a), SBA 504, conventional) to fill rate, amortization and loan-to-price as the calculator does.

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>",
      "adr": "<adr>",
      "occupancy_pct": "<occupancy_pct>",
      "price": "<price>"
    },
    "name": "size_hotel_loan"
  }
}

Input Schema

NameRequiredDescriptionDefault
adrYesAverage daily rate in dollars, e.g. 89.
loanNoLoan requested in dollars. Default: price times the maximum loan-to-price.
brandNoFranchise brand name or slug (e.g. "Super 8", "comfort-inn") to fill franchise fees from its FDD. Omit for an independent with no franchise fees.
priceYesPurchase price or value in dollars, e.g. 3200000.
roomsYesRooms (keys), e.g. 64.
programNoFills rate, amortization and maximum loan-to-price the way the calculator's program buttons do. Default sba_7a.sba_7a
opex_pctNoOperating costs as a percent of total revenue, excluding franchise fees, management, taxes, insurance and reserve. Default 56 (the calculator example; use the trailing-12 P&L).
rate_pctNoInterest rate, percent. Overrides the program rate.
insuranceNoInsurance, dollars a year. Default 0: pass the real figure or NOI is overstated.
dscr_targetNoLender's minimum debt service coverage, e.g. 1.25. Default 1.25 (SBA 7(a) hotel acquisition).
max_ltv_pctNoLender's maximum loan to price or value, percent. Overrides the program.
reserve_pctNoFF&E reserve as a percent of total revenue. Default 4.
occupancy_pctYesOccupancy, percent, e.g. 62.
management_pctNoManagement fee as a percent of total revenue. Default 0 (owner-operated).
property_taxesNoProperty taxes, dollars a year. Default 0: pass the real figure or NOI is overstated.
franchise_fee_pctNoFranchise fees as a percent of rooms revenue. Overrides the brand.
other_revenue_pctNoOther revenue as a percent of rooms revenue (vending, pet fees, meeting room). Default 2.
amortization_yearsNoAmortization in years. Overrides the program term.
franchise_fee_per_room_monthNoFranchise fees per room per month in dollars. Overrides the brand.

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 cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the computation contract: defaults mirror the calculator example, brand/program act as fill-in presets, and explicit overrides win. It also warns that omitting insurance or property taxes overstates NOI, which is genuine behavioral guidance rather than restated annotation.

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?

Two sentences, front-loaded with the verb and the output list, then the preset/override mechanics. The output enumeration is long but every item is a distinct returned metric, so it earns its space; the sentence is dense but not padded.

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 19 parameters and no output schema, the description carries the return-value burden and does it well by naming NOI, DSCR, max supportable loan, the binding constraint, cap rate, price per key and breakeven occupancy. It does not state units or the failure mode for infeasible deals (e.g., negative DSCR), which is the only remaining gap for a tool of this complexity.

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 baseline is 3; the description earns more by explaining cross-parameter interaction the per-field descriptions cannot — brand fills franchise fees from its FDD, program fills rate/amortization/LTP, and the explicit override fields beat both. It also clarifies that loan defaults to price times max loan-to-price, tying the required and optional inputs together.

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?

Names a specific verb and resource ("Runs the motel.loans hotel loan sizer on your numbers") and enumerates the computed outputs, so the agent knows exactly what it gets back. It does not name its siblings (get_sba_hotel_loan_terms, get_franchise_costs, compare_franchise_costs) to say how it differs from them, 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 implied by the mechanics described — "Pick a brand to fill franchise fees from its FDD and a program ... to fill rate, amortization and loan-to-price" — which tells the agent how to drive the tool but not when to choose it over get_sba_hotel_loan_terms or compare_franchise_costs. No explicit when-not or prerequisite statement is given.

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