Skip to main content
Glama

Xearno Tools

UK Capital Gains Tax Calculator (2025-26 & 2026-27)

uk_capital_gains_tax
Read-only

Capital Gains Tax on shares, crypto, property, or a business sale — current £3,000 allowance, the 18%/24% rate split driven by your income, and the BADR 14% → 18% ramp. Computes UK Capital Gains Tax on a disposal using the current rules: the £3,000 annual exempt amount, the 18%/24% rates that have applied to ALL assets since 30 October 2024, the income-stacking rule that decides how much of the gain falls at 18% vs 24%, and Business Asset Disposal Relief with its stepping rate (14% in 2025-26, 18% from 6 April 2026) and £1 million lifetime limit. General AI reliably gets this wrong three ways at once — quoting the abolished £12,300 allowance, the dead 10%/20% share rates, and a BADR rate from the wrong year — and answers without asking for your taxable income, the input that actually sets the rate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gainNoTotal gain on the disposal (£) Proceeds minus what you paid minus allowable costs (buying/selling fees, improvement costs). The gain, not the sale price.
assetTypeNoWhat are you selling? BADR (Business Asset Disposal Relief) needs, broadly: 2 years of ownership, and for company shares at least 5% of shares and votes while being an officer or employee — check the full conditions. Selling the home you’ve always lived in? Usually NO CGT at all (Private Residence Relief) — this tool is for property that was never, or not always, your main home.other
disposalDateNoWhen are you disposing (tax year)? The BADR rate steps 14% → 18% at this boundary (6 April 2026) — the disposal date IS a rate input now, not admin detail. Main 18%/24% rates and the £3,000 allowance are the same in both years.2026-27
taxableIncomeNoYour taxable income this year (£) Income AFTER the personal allowance — roughly your salary minus £12,570. This is the hidden input: the gain stacks on top of it, and it decides how much falls in the basic band at 18% vs above it at 24%.
badrLifetimeUsedNoBADR lifetime relief already claimed (£) Only matters for BADR disposals. Gains you have already claimed BADR on, ever — the relief has a £1 million lifetime limit.
otherGainsUsedAeaNoAlready used the £3,000 allowance this year? The annual exempt amount is per tax year across all your disposals, not per disposal.no

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint=true annotation, the description discloses key behaviors: use of £3,000 allowance, 18%/24% rate split with income-stacking, BADR stepping rates, and lifetime limit. It also notes that users must input taxable income as it determines the rate. No contradictions 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long (over 150 words) but well-structured with key facts front-loaded and warnings embedded. It could be slightly more concise, but every sentence adds value given the complexity of CGT rules. The structure is logical.

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 (6 parameters, no output schema), the description thoroughly explains inputs, common pitfalls, and computation logic. It covers all parameters and provides enough detail for an agent to select and invoke the tool correctly. No output schema is needed as the purpose is straightforward.

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% with descriptions for each parameter. The description adds extra semantic context, especially for taxableIncome (explaining its role as the hidden input for rate determination) and assetType (clarifying BADR conditions and main home exemption). This adds meaning beyond the 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 explicitly states it computes UK Capital Gains Tax on a disposal using current rules, and lists asset types (shares, crypto, property, business sale). It distinguishes itself from sibling tools by being a specific tax calculator, and the title includes tax years. This is a specific verb+resource with clear scope.

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 explains when to use (for disposals of various assets) and warns about common mistakes (abolished allowance, dead rates). It implies when not to use for main home (Private Residence Relief), but does not explicitly mention alternative tools in sibling list for other tax scenarios. Still, context is clear.

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.

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