Skip to main content
Glama

SA Build & Renovation Costs

Check if a fix-and-flip deal adds up

renovation_flip_check
Read-only

Checks a buy-renovate-sell deal in South Africa: purchase price, renovation estimate, transfer duty and costs, holding costs and selling costs (agent commission) against expected resale value. Returns profit, margin and the maximum sensible offer for a target margin.

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": {
      "purchase_price": "<purchase_price>",
      "renovation_cost": "<renovation_cost>",
      "expected_resale": "<expected_resale>"
    },
    "name": "renovation_flip_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
months_heldNoMonths from purchase to sale, for holding costs. Default 6
purchase_priceYesPrice paid for the property, in rand
expected_resaleYesExpected selling price after renovation, in rand
renovation_costYesTotal incl. VAT, e.g. from estimate_works
target_margin_pctNoTarget profit as % of total cost
agent_commission_pctNoIncl. VAT
monthly_holding_costNoRates, levies, insurance, utilities, bond interest. Default 1% of purchase price

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / expected_resale / description
      Added value: +"Expected selling price after renovation, in rand"
    • addedInput schema / properties / months_held / description
      Added value: +"Months from purchase to sale, for holding costs. Default 6"
    • addedInput schema / properties / purchase_price / description
      Added value: +"Price paid for the property, in rand"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: it discloses the South African jurisdiction-specific cost treatment (transfer duty included, agent commission as selling cost) and enumerates the analytical outputs, so an agent knows this computes rather than merely echoes inputs.

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, zero filler, with the scope and jurisdiction front-loaded and the return values stated last. Every clause carries information an agent needs.

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 seven parameters and no output schema, the description must describe returns, and it does (profit, margin, maximum sensible offer for a target margin). Jurisdiction and cost coverage are stated. It stops short of noting assumptions such as default holding cost or VAT treatment, which matter for interpreting results, but the essentials are present.

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 each of the seven parameters is already documented. The description restates the same cost buckets (purchase price, renovation, holding, commission) without adding syntax, units, or format detail beyond the schema; the one new fact, that transfer duty is computed internally, is minor. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Checks') and a specific resource ('a buy-renovate-sell deal in South Africa'), then lists exactly which cost components are evaluated and what comes back (profit, margin, maximum sensible offer). That is clearly distinct from the sibling cost-estimation tools, which produce cost figures rather than deal-level profitability.

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?

Usage context is clear: this is the tool for judging whether a flip deal stacks up, with the required inputs implied as the deal's knowns. There is no explicit statement of when not to use it or which sibling to reach for first (e.g., estimate_works for the renovation figure is only hinted at in the schema, not the description).

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