Skip to main content
Glama
tresor4k

macalc

calculate_stamp_duty_uk

Calculate UK Stamp Duty Land Tax (SDLT) for home buyers. Enter property price and first-time buyer status to get SDLT due and effective rate. Plan your purchase costs.

Instructions

Compute UK Stamp Duty Land Tax (SDLT). Use for UK home buyers. Inputs: property price, first-time-buyer flag, second-home flag. Returns SDLT due and effective rate. See list_bundles for related 'finance-uk' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
priceYesProperty purchase price in GBP
first_time_buyerNoWhether buyer is a first-time buyer (default false)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior3/5

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

Annotations are absent, so description must cover behavior. It states returns SDLT due and effective rate, but does not disclose if the tool is a pure computation with no side effects or authorization needs. For a calculator, this is moderately transparent.

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?

The description is concise with multiple short sentences, front-loaded with purpose, and includes inputs and outputs. No unnecessary words; every sentence adds value.

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

Completeness3/5

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

Given tool simplicity and presence of output schema, the description provides adequate context for usage. However, the incorrect mention of a nonexistent parameter reduces completeness and could confuse the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 2 parameters (price, first_time_buyer) with 100% description coverage. However, the description erroneously mentions a 'second-home flag' not in the schema, misleading parameter semantics. The description adds no useful info beyond schema.

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 UK Stamp Duty Land Tax for home buyers, with verb 'Compute' and specific resource 'UK Stamp Duty Land Tax'. It lists key inputs and outputs, distinguishing it from sibling tools like other calculate_* tools.

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 says 'Use for UK home buyers', providing clear context, and directs to list_bundles for related calculators, offering alternative guidance. However, it doesn't explicitly state when not to use the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server