Skip to main content
Glama

SA Property Costs

Estimate total once-off costs of buying property

purchase_costs
Read-only

Estimates once-off costs of buying a South African property: transfer duty (exact), plus estimated conveyancing (transfer) fees, Deeds Office fees and bond registration costs. Fees are estimates — attorneys quote from the LSSA guideline.

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>"
    },
    "name": "purchase_costs"
  }
}

Input Schema

NameRequiredDescriptionDefault
bond_amountNoHome loan amount, 0 if cash
purchase_priceYesPurchase price in rand
seller_is_vat_vendorNoTrue if the seller is a VAT vendor selling in the course of business (VAT applies instead of transfer duty). Default false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / purchase_price / description
      Added value: +"Purchase price in rand"
    • addedInput schema / properties / seller_is_vat_vendor / description
      Added value: +"True if the seller is a VAT vendor selling in the course of business (VAT applies instead of transfer duty). Default false"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: transfer duty is exact while the other components are estimates, and attorneys quote from the LSSA guideline. It does not state whether the result is itemized or a single total, which is the one behavioral gap.

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 tight sentences: the scope and cost components come first, followed by the accuracy caveat and its source. No redundant restatement of the name or title, and every clause contributes 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?

For a read-only three-parameter calculator with full schema coverage and no output schema, the description covers jurisdiction, cost components, and the exact-vs-estimate distinction well. The remaining gap is that an agent does not know whether to expect a single total or a per-component breakdown in the response.

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 all three parameters including the VAT-vendor flag and the bond_amount default of 0 are already documented. The description adds only indirect meaning — 'transfer duty (exact)' hints that the VAT-vendor path swaps duty for VAT — but gives no explicit parameter guidance beyond the schema. Baseline 3 applies when the schema carries this load.

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?

States a specific verb (estimates) and resource (once-off costs of buying a South African property) and enumerates the exact cost components covered: transfer duty, conveyancing fees, Deeds Office fees, bond registration. This scope listing also implicitly separates it from the sibling transfer_duty tool, which covers only one of those components.

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 — an agent can infer this is for total upfront purchase-cost estimation rather than monthly repayments (bond_repayment) or ongoing municipal_rates. However, no sentence says when to use this versus transfer_duty, or when a user just wants the duty component alone. The VAT-vendor scenario is handled through the schema parameter rather than described as a usage condition.

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