Skip to main content
Glama

Worth Sheet: apartment building value at today's loan rates

Value an apartment building at today's loan rates

value_at_rate
Read-onlyIdempotent

Runs the Worth Sheet valuation worksheet for a 5+ unit apartment building: from a rent roll and a year of expenses (or a known NOI) it returns NOI, expense ratio, value across your cap rate range, the price a financed buyer can carry at the latest 10-year Treasury plus a lender spread (80% LTV, 1.25x DSCR by default), per-unit value, and the refinance loan the income supports against your balance. An estimate from your numbers, not an appraisal.

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": {
      "cap_rate_low_pct": "<cap_rate_low_pct>",
      "cap_rate_high_pct": "<cap_rate_high_pct>"
    },
    "name": "value_at_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dscrNoMin debt service coverage, times. Default 1.25 (both agencies' term sheets).
unitsNoNumber of units, for per-unit value when you give noi_annual.
ltv_pctNoMax loan-to-value, percent. Default 80 (Fannie Mae and Freddie Mac conventional term sheets).
unit_mixNoRent roll by unit type, e.g. [{"units":12,"monthly_rent":1250},{"units":16,"monthly_rent":1500}]. Give this or noi_annual.
tax_resetNoTrue if a sale resets the property tax bill to a share of the price; value is then solved with taxes at tax_rate_pct of price.
noi_annualNoNet operating income per year in US dollars, if you already know it. Give this or unit_mix (not both).
spread_pctNoLender spread over the 10-year, percent. Default 1.75, the worksheet's placeholder (not a quote).
vacancy_pctNoVacancy and bad debt, percent of gross. Default 5.
loan_balanceNoYour current loan balance, US dollars, to compare against the refinance loan. Optional.
tax_rate_pctNoTax rate on the new value, percent of price (county millage as a percent). Default 1.5. Used only when tax_reset is true.
management_pctNoManagement, percent of collected income; charge it even if self-managed. Default 5.
payroll_annualNoPayroll per year, US dollars. Default 0.
cap_rate_low_pctYesLow end of the cap rate range brokers quote for similar buildings, percent, e.g. 5.5. No government source publishes cap rates.
insurance_annualNoInsurance per year, US dollars. Default 0.
utilities_annualNoOwner-paid utilities per year, US dollars. Default 0.
cap_rate_high_pctYesHigh end of the cap rate range, percent, e.g. 7.
reserves_per_unitNoReplacement reserves per unit per year, US dollars. Default 300.
treasury_10yr_pctNo10-year Treasury yield to use, percent. Default: the latest daily par yield the site has (U.S. Treasury).
admin_other_annualNoAdmin, legal and other expenses per year, US dollars. Put any lump-sum expense total (excluding property taxes) here. Default 0.
amortization_yearsNoAmortization in years. Default 30.
other_income_monthlyNoOther income per month (laundry, parking, fees), US dollars. Default 0.
property_taxes_annualNoProperty taxes per year, US dollars. Default 0. With noi_annual, needed only for tax_reset.
repairs_maintenance_annualNoRepairs, maintenance and turnover per year, US dollars. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the result is an estimate from supplied numbers, not an appraisal, and notes the latest Treasury default, which is useful behavioral context without contradicting annotations.

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?

The purpose and outputs are front-loaded in a compact two-sentence description despite the tool's complexity. Every clause carries relevant information, and the appraisal caveat is appropriately placed at the end.

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 no output schema, the description does the important work of naming the returned metrics: NOI, expense ratio, value range, financed-buyer price, per-unit value, and refinance loan. It is complete enough for invocation, though output formatting is not specified.

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%, so the schema itself documents all 23 parameters thoroughly. The description reinforces the main inputs and defaults but does not add much parameter-level detail beyond what the schema already provides.

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?

States a specific verb and resource: runs a named valuation worksheet for 5+ unit apartment buildings and lists the main outputs. It is clear what the tool does, but it does not explicitly differentiate itself from the sibling rate tools.

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?

Makes the usage context clear: rent roll plus a year of expenses, or a known NOI. It does not explicitly say when to choose this over get_rates_and_loan_limits or rate_sensitivity, but the input conditions are clear.

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