Skip to main content
Glama

Custom Solutions

Flip profit

compute_flip_profit
Read-onlyIdempotent

Profit on a buy, fix and sell: the net sale after selling costs, less price, purchase costs, repairs, holding costs and points, with the cash needed, the return on that cash and, with min_profit_pct, the most to pay and still keep that profit. Holding costs are what most flip estimates miss: interest on an interest-only loan plus tax, insurance and utilities for every month held, with months rounded up. Send price, arv, repairs, months and selling_costs_pct; optionally purchase_costs, holding_costs_monthly, loan_pct_of_price, loan_pct_of_repairs, rate_pct, points_pct and min_profit_pct. Omitted loan inputs mean an all-cash flip.

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>",
      "arv": "<arv>",
      "repairs": "<repairs>",
      "months": "<months>",
      "selling_costs_pct": "<selling_costs_pct>"
    },
    "name": "compute_flip_profit"
  }
}

Input Schema

NameRequiredDescriptionDefault
arvYesValue after repairs (ARV), e.g. 260000
priceYesPurchase price, e.g. 150000
monthsYesMonths to finish and sell, e.g. 5 (rounded up, at least 1)
repairsYesAll repairs plus resale prep, e.g. 45000
rate_pctNoInterest-only rate in percent, e.g. 11
points_pctNoPoints as a percent of the loan, e.g. 2
min_profit_pctNoMinimum profit as a percent of ARV, e.g. 12, for the most to pay
purchase_costsNoClosing and other purchase costs, e.g. 3500
loan_pct_of_priceNoShare of the price the lender funds, in percent, e.g. 85
selling_costs_pctYesSelling costs as a percent of the sale price, e.g. 7
loan_pct_of_repairsNoShare of repairs the lender funds, in percent, e.g. 100
holding_costs_monthlyNoTax, insurance and utilities per month while held, e.g. 400

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 establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description goes further by disclosing the rounding rule ('months rounded up'), the content of holding costs (interest-only interest plus tax, insurance, utilities), and the outputs produced (cash needed, return on cash, and 'most to pay' with min_profit_pct). It does not describe result formatting or edge-case behavior such as negative-profit returns. This is meaningful added context beyond the 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?

The result definition and the key modeling insight about holding costs are front-loaded, which is the right order. The final sentence partially restates the schema's required/optional split, which is mild redundancy, and the sentences are long and clause-heavy. It is dense but each part carries information; trimming the parameter roster would tighten it without losing meaning.

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 12-parameter calculator with no output schema, the description does the needed work: it enumerates the outputs (profit, cash needed, return on cash, max price at min_profit_pct) and explains the loan-vs-cash input branch. What is missing is a brief statement of output structure/units or handling of loss scenarios. Given the annotations already cover side-effect behavior, this is nearly complete.

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 already 100%, so the baseline is 3, but the description adds cross-parameter meaning the per-property docs cannot: the loan inputs form an optional group whose omission selects an all-cash flip, and min_profit_pct switches on the max-purchase-price output. It also clarifies what holding_costs_monthly excludes (loan interest is separate) and how months are rounded. It does not explain how loan_pct_of_price and loan_pct_of_repairs interact numerically.

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 opens with a precise definition: net sale after selling costs, less price, purchase costs, repairs, holding costs and points, plus cash needed and return on cash. That is a specific computational verb and resource, not a restatement of the name. It does not name a sibling (e.g. compare_rental_vs_flip or compute_max_offer_at_cap_rate) to route the agent, so it stops short of full sibling differentiation.

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 states which inputs are required (price, arv, repairs, months, selling_costs_pct) and which are optional, and importantly discloses the selection rule for the loan branch: 'Omitted loan inputs mean an all-cash flip.' That is real context for choosing an input combination. There is no explicit when-not-to-use guidance or named alternative tool for comparing scenarios.

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