Skip to main content
Glama

Xearno Tools

by tools.xearno

Singapore Property Stamp Duty (BSD + ABSD + SSD)

singapore_property_stamp_duty
Read-only

Buyer’s, Additional Buyer’s, and Seller’s Stamp Duty at the current IRAS rates — including the 60% foreigner ABSD and the 2025 four-year SSD. Computes Singapore residential stamp duty at the rates actually in force: BSD on the marginal bands up to 6%, ABSD by your exact buyer profile and property count (foreigners pay a flat 60% since 27 Apr 2023 — double what most AI models still quote), and SSD by your acquisition-date cohort (purchases on/after 4 Jul 2025 are on a new 16/12/8/4 four-year schedule). The inputs that swing the answer are ones buyers rarely know matter: the citizenship tier (a US citizen gets Singapore Citizen treatment under the FTA; a US green-card holder does not), how many residential properties you already hold (any fractional interest counts in full), and for joint purchases, the co-buyer whose rate governs the entire price.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoBuying or selling?buy
priceNoPrice / market value (the higher of the two) (S$) Stamp duty is charged on the higher of the price and the market value — for buying and selling alike.
acqYearNoAcquisition year Selling-mode only. The acquisition date is the day you accepted/exercised the Option to Purchase (or signed the Sale & Purchase Agreement) — not the grant of the option. It selects which SSD schedule applies. Acquisitions before 14 Jan 2011 are not modeled (any sale now is past every tier anyway).
profileNoBuyer profile The decisive input — it moves ABSD between 0% and 60% of the price. The FTA carve-out is exact: US CITIZENS qualify (green-card holders do NOT); for Iceland, Liechtenstein, Norway and Switzerland, both nationals and PRs qualify. Buying-mode only.sc
acqMonthNoAcquisition month Selling-mode only. 1–12.
saleYearNoSale year Selling-mode only. The year you (will) contract to sell.
saleMonthNoSale month Selling-mode only. 1–12.
propertiesOwnedNoResidential properties already owned in Singapore Count before this purchase. Any fractional interest — even 1% on a parent’s flat — counts as one full property. Overseas property does not count. Buying-mode only.
jointHighestRateNoJoint purchase — co-buyer with a higher ABSD profile In a joint purchase the buyer with the HIGHEST applicable ABSD rate sets the rate for the entire price — not just their share. The co-buyer’s rate here is computed at the same properties-owned count as yours; if they own more, rerun with their count to check whose rate governs. Buying-mode only.none

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, but the description adds extensive behavioral context: it uses current IRAS rates, computes based on buyer profile and property count, handles joint purchases and FTA provisions, and applies correct SSD schedules by acquisition year. No contradiction with annotations.

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?

Despite being relatively long, every sentence adds crucial information. The first sentence states the core purpose, and subsequent details are relevant and well-structured. No redundant or tautological content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (9 parameters, no output schema), the description covers all critical aspects: buy/sell modes, rate determination, special cases (FTA, joint purchase), and common errors. It provides enough context for an AI agent to understand and use the tool correctly.

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 100%, so baseline is 3. The description adds significant value by explaining the impact of each parameter (e.g., profile moves ABSD 0-60%, propertiesOwned counts fractional interests in full, jointHighestRate governs entire price). This goes beyond the schema's parameter descriptions.

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 clearly states the tool computes Buyer's, Additional Buyer's, and Seller's Stamp Duty for Singapore residential property at current IRAS rates. It specifies the exact rates and rules, distinguishing it from generic tax calculators and sibling tools like UK stamp duty.

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?

The description implicitly guides usage by explaining critical inputs (profile, properties owned, joint purchase) and common mistakes (e.g., US citizen vs green card holder, correct SSD schedule). It does not explicitly state when not to use (e.g., non-residential), but the scope is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Xearno Tools toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Each tool targets a distinct niche (e.g., specific country tax rules, loan types, or legal calculations), with detailed descriptions that clarify boundaries. However, the large number of tools (66) could cause some confusion for an agent trying to select the right one for a general query, especially when multiple tools relate to the same country.

Naming Consistency4/5

Tool names follow a mostly predictable pattern: lowercase words separated by underscores, often starting with a country name (e.g., 'uk_stamp_duty_sdlt') or a topic (e.g., 'compound_growth'). There are minor deviations, such as abbreviations ('npv_irr', 'sip') and varying use of verbs, but overall the naming is clear and consistent.

Tool Count3/5

At 66 tools, the server is unusually large and covers an extensive range of financial and legal calculators. While each tool justifies its existence, the count exceeds the typical well-scoped range (3–15), making the server feel bloated. A more modular design might improve coherence.

Completeness4/5

The tool set covers a wide array of domains: personal income taxes, property taxes, loan calculations, investment returns, and specific country regulations. Minor gaps exist (e.g., missing tools for corporate taxes, general retirement planning, or insurance), but the overall coverage is thorough and addresses many niche scenarios that general AI handles poorly.

Resources