Skip to main content
Glama

Stamp Duty (SDLT) calculator — England & Northern Ireland

calculate_stamp_duty
Read-onlyIdempotent

Calculate Stamp Duty Land Tax for a residential purchase in England or Northern Ireland. Input the price (GBP) and buyer_type: first_time_buyer, standard (moving home, replacing a main residence) or additional_property (second home / buy-to-let); non_uk_resident adds the non-resident surcharge. Returns the total tax, effective rate and the band-by-band breakdown. NOT for Scotland (LBTT) or Wales (LTT) — say so rather than quoting this figure for a property there. Indicative only, not tax advice.

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

Input Schema

NameRequiredDescriptionDefault
priceYesPurchase price in GBP
buyer_typeYesfirst_time_buyer | standard | additional_property
non_uk_residentNotrue if the buyer is not UK resident

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the bar is lower; the description still adds value by disclosing the return contents (total tax, effective rate, band-by-band breakdown) and the liability caveat "indicative only, not tax advice". It does not mention a tax-year/rate-version or how rates are sourced, which is the one material omission.

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?

Front-loaded with the action and scope, then parameters, then returns, then exclusions and disclaimer — a sensible ordering that is dense with no filler. Slightly long single block, and the buyer_type re-listing partially duplicates the schema.

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 3-parameter, no-output-schema calculator, the definition covers scope, inputs, return shape and caveats, which is close to complete. It stops short on whether commercial/non-residential or shared-ownership purchases are out of scope, leaving a narrow but real gap given the residential-only framing.

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 would be 3, but the description earns above baseline by expanding the enum values in plain language ("moving home, replacing a main residence", "second home / buy-to-let") and by stating that non_uk_resident adds a surcharge. It does not explain the interaction between first_time_buyer and non_uk_resident, which leaves one ambiguity.

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 and resource ("Calculate Stamp Duty Land Tax") with a precise jurisdictional and property-type scope (residential, England or Northern Ireland). No sibling tool does a tax calculation, and the description makes the boundary unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance via the buyer_type meanings and an explicit when-not: not for Scotland (LBTT) or Wales (LTT), with an instruction to say so rather than reuse the figure. That is a genuine exclusion plus a fallback behaviour, not just context.

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