Skip to main content
Glama

Custom Solutions

Rental or flip

compare_rental_vs_flip
Read-onlyIdempotent

Whether a property earns more as a rental held for a number of years or as a flip: the rental's total profit (cash flow over the hold plus sale proceeds after selling costs and the loan payoff, less the cash invested) against the flip's profit, with the difference and the rental's yearly return. The comparison is only fair over the same money: the rental side needs its loan balance at sale and the growth of rent, expenses and value. Send price, noi, annual_debt_service, cash_invested, hold_years and flip_profit; optionally arv, loan_amount, rate_pct, amort_years, growth_pct, value_growth_pct and selling_costs_pct. Without arv the price is grown.

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>",
      "noi": "<noi>",
      "annual_debt_service": "<annual_debt_service>",
      "cash_invested": "<cash_invested>",
      "hold_years": "<hold_years>",
      "flip_profit": "<flip_profit>"
    },
    "name": "compare_rental_vs_flip"
  }
}

Input Schema

NameRequiredDescriptionDefault
arvNoValue after repairs, e.g. 180000; the price is used when absent
noiYesStabilized NOI per year, e.g. 14000
priceYesPurchase price, e.g. 150000
rate_pctNoLoan rate in percent, e.g. 7.25
growth_pctNoYearly growth of rent and expenses in percent, e.g. 3
hold_yearsYesYears held before selling, 1 to 30, e.g. 7
amort_yearsNoAmortization in years, e.g. 30
flip_profitYesThe flip's profit, e.g. 24000
loan_amountNoLoan amount, e.g. 120000, for the balance at sale
cash_investedYesCash put into the rental, e.g. 40000
value_growth_pctNoYearly growth of the property value in percent, e.g. 3
selling_costs_pctNoSelling costs at the end of the hold in percent, e.g. 7
annual_debt_serviceYesPrincipal and interest per year, e.g. 9800 (0 for no loan)

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 this a read-only, idempotent, closed-world computation, so the description is not obliged to cover safety. What it does add is valuable: the exact accounting model behind the rental side, what the response contains (rental profit, flip profit, difference, yearly return), and the fallback rule 'Without arv the price is grown' — a genuine behavioral detail found nowhere in the schema. It leaves the units of 'yearly return' (percent vs dollars) and any error/precondition behavior unspecified.

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?

The purpose is front-loaded in the first clause, and the two dense sentences cover model, fairness requirement, and parameter inventory with little waste. The comma-spliced lists make it slightly heavy to parse, but nothing is redundant with structured fields.

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, no-output-schema calculator, the description covers what an agent needs to assemble a valid call and what comes back (two profits, the difference, yearly return). The remaining gap is output interpretation detail — sign convention and units of the return figure — which matters when there is no 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?

With 100% schema coverage the baseline is 3, but the description goes further by partitioning the parameters into a required set (price, noi, annual_debt_service, cash_invested, hold_years, flip_profit) and an optional set, and by explaining the purpose of optional ones — loan balance at sale and growth of rent/expenses/value — rather than just listing them. It also clarifies arv's default behavior beyond the schema's 'the price is used when absent'.

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 a specific comparison ('rental vs flip') and spells out exactly which quantities are being compared: the rental's total profit (cash flow over hold + sale proceeds after selling costs and loan payoff, less cash invested) against flip_profit, plus the difference and yearly return. It is clearly not compute_flip_profit, since that sibling's output is one of this tool's required inputs, though it never names the distinction explicitly.

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 gives real usage context by explaining the fairness condition ('the comparison is only fair over the same money') and therefore why loan_amount, growth_pct and value_growth_pct matter even though they are optional. It does not state when a caller should prefer this over separate calls to compute_flip_profit or a rental-only tool, so it stops short of explicit alternatives or exclusions.

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