Skip to main content
Glama

Xearno Tools

by tools.xearno

UK Notice Pay Calculator

uk_notice_pay
Read-only

How many weeks’ notice you’re owed, what it pays, and how much of it is taxed. Your employer owes you notice when they end your job: one week if you have been there under two years, then one week for every full year, up to twelve. This works out your weeks and what they pay — and then the part people get wrong. Notice pay is not covered by the £30,000 tax-free allowance that shelters redundancy pay; if it is paid in lieu it is taxed as normal earnings. And if your employer has gone bust and the state pays instead, the amount is capped at £751 a week and reduced by benefits you claimed — or could have claimed, even if you never applied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearsNoComplete years worked there Full years of continuous employment. Part years do not add a week — at 4 years 11 months you get 4 weeks, not 5.
nationNoWhere you work Notice periods are the same everywhere in the UK. Only the insolvency weekly cap differs: £751 in Great Britain, £783 in Northern Ireland.gb
taxRateNoYour income tax rate Used to estimate the tax on your notice pay. National Insurance comes off on top of this and is not included in the estimate.20
benefitsNoBenefits you got (or could have got) during notice (£ total) Insolvency claims only. Universal Credit or Jobseeker’s Allowance for the notice period is deducted — and it is deducted even if you never applied, unless you were refused and send the rejection letter.
situationNoHow is your notice being handled? The decisive input: it changes both the amount and the tax. Paid in lieu is taxed as earnings with no £30,000 shelter. The insolvency route is capped weekly and reduced by benefits.pilon
weeklyPayNoYour weekly pay before tax (£) Gross, before tax. Monthly salary ÷ 4.333 if that is easier.
contractWeeksNoNotice in your contract (weeks, if longer) Leave 0 to use the statutory minimum. Many contracts say one or three months — that is 4.3 or 13 weeks, and the longer of the two always wins.

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses statutory notice calculation (one week per year up to 12), tax treatment (no £30,000 shelter, taxed as normal earnings), insolvency cap (£751/week in Great Britain), and benefit deduction even if unclaimed. This adds significant context beyond what annotations provide.

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 a single, well-front-loaded paragraph. It starts with a summary question, then efficiently walks through the statutory rule, tax nuance, and insolvency specifics. Every sentence contributes new information; the length is justified by the tool's complexity.

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?

Covers key scenarios: statutory notice, paid-in-lieu tax, and insolvency (cap and benefit deduction). No output schema exists, but the description states it works out weeks, pay, and tax, which implies expected outputs. Combined with the detailed input schema, the description is complete for an agent to select and use the tool.

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

Parameters3/5

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

Schema description coverage is 100%, with each parameter already well-documented (e.g., 'years' explains part years, 'nation' explains cap difference, 'benefits' explains insolvency deduction). The description adds general context but does not provide additional parameter-level semantics beyond what the schema already contains.

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 opens with a clear statement of what the tool does: 'How many weeks’ notice you’re owed, what it pays, and how much of it is taxed.' It explicitly contrasts notice pay with redundancy pay, noting the £30,000 tax-free allowance distinction, which differentiates it from sibling tools like uk_statutory_redundancy_pay.

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 the tool is relevant: when an employer ends a job and owes notice, including paid-in-lieu and insolvency scenarios. It distinguishes notice pay from redundancy pay conceptually, but does not explicitly name an alternative tool or state 'use this tool when...' / 'not when...'. Clear context without explicit exclusions.

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