Skip to main content
Glama

SA Property Costs

Calculate SARS transfer duty

transfer_duty
Read-only

Calculates South African transfer duty payable to SARS on a property purchase, using the current sliding scale (no duty up to R1,210,000). Notes when VAT applies instead (seller is a VAT vendor).

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": "transfer_duty"
  }
}

Input Schema

NameRequiredDescriptionDefault
purchase_priceYesRand, excl. VAT
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. Changed1 schema field changed
    • 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

A3.9/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 safety is covered. The description adds substantive domain behavior beyond that: a sliding scale, the zero-duty threshold of R1,210,000, and the VAT-vendor override. It does not say how current the scale is or how staleness is handled, which is the one meaningful gap.

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?

Two tight sentences with the core purpose front-loaded and the threshold placed early. The closing VAT note partially duplicates the seller_is_vat_vendor parameter description, which is a small redundancy rather than a flaw.

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 two-parameter read-only calculator with no output schema, the description covers the domain rules an agent needs. It is slightly incomplete in not indicating what is returned, especially whether the result is zero or a VAT note when seller_is_vat_vendor is true.

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 coverage is 100%, so both parameters are already documented in the schema. The description reinforces the R1,210,000 threshold and the VAT-vendor condition but adds no syntax, units, or edge-case detail beyond the schema text. Baseline 3 applies when the schema does the heavy lifting.

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: 'Calculates South African transfer duty payable to SARS on a property purchase.' That is clearly distinct from bond_repayment and municipal_rates. It does not address overlap with purchase_costs, which could plausibly also cover transfer duty, so sibling differentiation is inferred rather than stated.

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?

Gives a clear usage context (property purchase transfer duty) plus an explicit exclusion: when the seller is a VAT vendor, VAT applies instead of transfer duty. No sibling alternatives are named, but the internal when-not condition is a meaningful routing signal.

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