Skip to main content
Glama

United Kingdom Salary and Income Tax Calculator

Employer cost of a salary in United Kingdom

employer_cost
Read-onlyIdempotent

What a salary in United Kingdom costs the employer (employer social contributions itemised), or the reverse: the gross salary a total budget allows. Give gross_annual or budget_annual.

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": "employer_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoWhere you live: ruk = England, Wales or Northern Ireland; scotland = Scotland. Default ruk.
childrenNoNumber of dependent children. Default 0.
postgradNoPostgraduate loan Default false.
tax_yearNoTax year. Offered: 2026 (final), 2025 (final), 2024 (final). Default 2026. A year that is not listed is not available for this country.
fx_per_eurNoExchange rate: 1 euro = this many GBP, for the euro amounts. Default 0.84 (indicative).
pension_pctNoVoluntary employee pension contribution through payroll, % of salary. Default 0.
bonus_annualNoYearly bonus in GBP. Default 0.
gross_annualNoGross yearly salary in GBP
student_loanNoStudent loan: none = None; plan1 = Plan 1; plan2 = Plan 2; plan4 = Plan 4 (Scotland); plan5 = Plan 5. Default none.
budget_annualNoTotal yearly employer budget in GBP, to find the gross salary it allows
child_benefitNoClaim Child Benefit. With children: Child Benefit is shown, and above £60,000 the charge that claws it back. Default true.
pension_methodNoHow pension is paid. Salary sacrifice saves tax and NI; net pay saves tax; relief at source is paid from net pay and HMRC adds 25%.: sacrifice = Salary sacrifice; netpay = Net pay arrangement; ras = Relief at source. Default sacrifice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tax_year
      Added value: +{
      +  "description": "Tax year. Offered: 2026 (final), 2025 (final), 2024 (final). Default 2026. A year that is not listed is not available for this country.",
      +  "enum": [
      +    2026,
      +    2025,
      +    2024
      +  ],
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond that: the tool itemises employer social contributions rather than returning a single figure, and it can solve in reverse from a budget. It still leaves open the resolution rule when both gross_annual and budget_annual are provided.

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?

Two sentences, zero filler, with the primary computation stated first and the inverse mode immediately after. The final imperative sentence doubles as an actionable instruction rather than padding.

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 12-parameter calculator with full schema coverage and no output schema, the description covers purpose and input-mode selection adequately. It partially compensates for the missing output schema by stating that employer contributions are itemised, though it does not sketch the return shape or note how region, pension method, and child benefit interact with the result.

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 the baseline is 3, but the description goes further by framing gross_annual and budget_annual as alternative input modes for opposite computation directions. That mutual-exclusivity hint is not present in the schema itself, where both appear as plain optional numbers, so the description adds real meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete computation (employer cost of a salary) plus its inverse (gross salary from a total budget), and the parenthetical about itemised employer social contributions makes the resource unambiguous. It does not explicitly name a sibling to differentiate from (e.g. net_salary or gross_for_target_net), so an agent must infer the boundary, but the employer-side framing is distinctive enough to separate it in practice.

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

Usage Guidelines3/5

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

The closing sentence 'Give gross_annual or budget_annual' tells the agent how to select the forward vs. reverse mode, which is genuine usage guidance. However, there is no explicit when-to-use vs. the salary/net calculators in the sibling set, no statement about what happens if both are supplied or neither is supplied, and no prerequisites.

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