Skip to main content
Glama

Stamp duty calculator

stamp_duty_calculator
Read-onlyIdempotent

Use this for stamp duty on a home in England or Northern Ireland, LBTT in Scotland or LTT in Wales: the tax band by band for a first time buyer, a home mover or an additional home, with first time buyer relief and where the next band starts. Give a price and a nation, or a home page address.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stamp_duty_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
homeNoA home page address from a search: its price, nation and builder offers are used.
priceNo
nationNoWhere the home is. Scotland pays LBTT and Wales LTT; England and Northern Ireland stamp duty.
additional_homeNoBuying while keeping another home: the higher rates.
non_uk_residentNo
first_time_buyerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety bar is low; the description adds value by disclosing what the result contains — band-by-band tax, first time buyer relief, and where the next band starts. It omits behavior for the zero-argument case and for the non_uk_resident flag, and says nothing about the source or currency of rates.

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?

A single front-loaded sentence that opens with "Use this for" and packs scope, regimes, buyer types and accepted inputs without filler. It is dense but every clause carries information; minor cost is that it is one long unbroken sentence.

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 calculator with no output schema and no required parameters, the description adequately conveys both the trigger conditions and the shape of the answer. Missing pieces are the non_uk_resident surcharge behavior and what happens if no price or home is supplied.

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?

With only 50% schema coverage, the description earns credit for explaining the price+nation versus home-address input modes, a relationship the schema does not make explicit (all six params are optional). It also maps buyer types to first_time_buyer and additional_home in prose. It leaves non_uk_resident entirely unexplained, which is the main gap.

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?

Names a specific resource (stamp duty / LBTT / LTT) and the exact scope — a home in England, Northern Ireland, Scotland or Wales — with the band-by-band breakdown and reliefs it returns. Naming the three devolved tax regimes clearly separates it from siblings like buying_costs or affordability_calculator.

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?

"Use this for stamp duty on a home in ..." gives a clear condition for calling, and "Give a price and a nation, or a home page address" tells the agent which input mode to use. It does not name an alternative tool or state exclusions (e.g. commercial property, non-residential), so it stops short of a 5.

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