Skip to main content
Glama

FreeDailyPro Tools

by com.freedailypro.api
OverviewDiscussionsAdmin

converters_uk_tax

Read-onlyIdempotent

UK income tax and Class 1 National Insurance 2026/27 with Scottish rates

Input Schema

NameRequiredDescriptionDefault
bonusNoA one-off bonus or overtime in the year, in pounds. Returns what it adds on its own in 'bonus'.
incomeYesGross annual salary in pounds.
taxCodeNoOptional PAYE tax code as printed on a payslip: 1257L, 1383M, 0T, BR, D0, D1, NT, K475, S1257L (Scotland), C1257L (Wales), SBR, SD0 to SD3. A code replaces the standard allowance. Omit it for the standard allowance and taper.
benefitsNoTaxable benefits in kind per year, in pounds: added to taxable pay for income tax, not charged employee National Insurance.
scotlandNotrue for Scottish income tax bands. Default false (England, Wales, Northern Ireland).
pensionPctNoYour pension contribution as a percent of salary.
pensionTypeNoHow the pension is taken: salary sacrifice (default, lowers tax and National Insurance), net pay arrangement (lowers tax only) or relief at source.
marriageAllowanceNoMarriage Allowance when no taxCode is sent: receive (tax reduced by up to £252) or give (£1,260 of allowance). Ignored when taxCode is sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / benefits
      Added value: +{
+  "description": "Taxable benefits in kind per year, in pounds: added to taxable pay for income tax, not charged employee National Insurance.",
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / bonus
      Added value: +{
+  "description": "A one-off bonus or overtime in the year, in pounds. Returns what it adds on its own in 'bonus'.",
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / marriageAllowance
      Added value: +{
+  "description": "Marriage Allowance when no taxCode is sent: receive (tax reduced by up to £252) or give (£1,260 of allowance). Ignored when taxCode is sent.",
+  "enum": [
+    "none",
+    "receive",
+    "give"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / taxCode
      Added value: +{
+  "description": "Optional PAYE tax code as printed on a payslip: 1257L, 1383M, 0T, BR, D0, D1, NT, K475, S1257L (Scotland), C1257L (Wales), SBR, SD0 to SD3. A code replaces the standard allowance. Omit it for the standard allowance and taper.",
+  "maxLength": 20,
+  "type": "string"
+}
  2. Changed4 schema fields changed
    • addedInput schema / properties / income / description
      Added value: +"Gross annual salary in pounds."
    • addedInput schema / properties / pensionPct
      Added value: +{
+  "description": "Your pension contribution as a percent of salary.",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / pensionType
      Added value: +{
+  "description": "How the pension is taken: salary sacrifice (default, lowers tax and National Insurance), net pay arrangement (lowers tax only) or relief at source.",
+  "enum": [
+    "sacrifice",
+    "netpay",
+    "ras"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / scotland
      Added value: +{
+  "description": "true for Scottish income tax bands. Default false (England, Wales, Northern Ireland).",
+  "type": "boolean"
+}
  3. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds the useful versioning constraint (2026/27 rules) and Scottish band support, but says nothing about whether results are estimates, which assumptions apply, or what is returned.

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?

A single front-loaded noun phrase with zero filler and the most decision-relevant facts (UK, tax year, Scotland) first. It is a fragment rather than structured prose, which limits it slightly, but nothing is wasted.

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

Completeness2/5

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

This is an 8-parameter tax engine with no output schema, yet the description gives no indication of what comes back (net pay, tax breakdown, NI split) or of any modelling assumptions. Given the complexity and the ambiguity against numerous tax siblings, one line is insufficient.

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 rich per-parameter text for taxCode, pensionType, marriageAllowance, benefits and bonus, so the schema carries the semantics. The description itself mentions no parameters at all, so the baseline of 3 is appropriate.

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?

States a specific domain and resource (UK income tax plus Class 1 National Insurance) and pins the tax year (2026/27) plus Scottish rate support. It is clearly distinguishable from the non-UK tax siblings by the word 'UK', though it never names those siblings explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance and no routing to alternatives such as converters_paycheck, converters_self_employment_tax, converters_state_tax, or converters_india_income_tax/us_income_tax. The agent must infer from the phrase 'UK income tax' alone that this is the right calculator.

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

All FreeDailyPro Tools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources