Skip to main content
Glama

borbur.net salary and tax calculators

UK take-home pay 2026/27

uk_net_salary
Read-onlyIdempotent

UK take-home pay in 2026/27 (England, Wales, Northern Ireland): income tax (personal allowance £12,570, tapered above £100,000; 20%, 40%, 45%) and employee National Insurance (8% to £50,270, 2% above). Source: https://borbur.net/tools/uk-salary-in-spain/

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "gross": "<gross>"
    },
    "name": "uk_net_salary"
  }
}

Input Schema

NameRequiredDescriptionDefault
grossYesGross annual salary in pounds sterling

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), and the description usefully adds the calculation basis: personal allowance £12,570 with taper above £100,000, the 20/40/45% bands, and 8%/2% NI thresholds. However it does not say what the result contains or whether pension contributions, student loans or Scotland are handled, and with no output schema that omission matters.

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 substantive tax parameters are packed into one front-loaded sentence with no filler, and the source URL is short and justified for a rate-dependent calculator. Slightly dense prose (rate/band lists inline) costs it the top score.

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?

For a single-input calculator this covers the tax year, jurisdiction and rate basis well. Because no output schema exists, the definition should describe what is returned (net figure only, or a breakdown), and it should state whether Scotland or other deductions are excluded — those gaps keep it at minimum-viable-plus.

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?

There is a single parameter with 100% schema coverage — 'Gross annual salary in pounds sterling' — which the description does not extend with units nuance, currency assumptions or boundary behavior. With one fully documented param, the schema does all the work and baseline 3 applies.

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 resource — UK take-home pay for 2026/27 — and pins the jurisdiction to England, Wales and Northern Ireland, which implicitly separates it from siblings like canada_net_salary or us_net_salary. It lacks an explicit verb ('calculate') and never names an alternative tool, so it stops short of a 5.

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?

Usage is only implied by the geographic scope: an agent can infer this is the UK (ex-Scotland) calculator. There is no explicit when-to-use, when-not-to-use, or pointer to a Scottish or non-UK sibling, leaving routing to inference from the name and parenthetical.

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