Skip to main content
Glama

Estimate self-employed tax

estimate_self_employed_tax
Read-only

Estimate UK income tax and Class 4 National Insurance for a sole trader from turnover and allowable expenses, with the take-home figure, effective and marginal rates, payments on account and tailored tips, from HMRC's published rates for the tax year. Works from the figures given, without a TapTax account.

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": {
      "turnover": "<turnover>"
    },
    "name": "estimate_self_employed_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
taxYearNoUK tax year, e.g. "2026-27" (6 April 2026 to 5 April 2027). Defaults to the current one.
expensesNoAllowable business expenses, in pounds (excluding mileage if businessMiles is given)
turnoverYesSelf-employed income before expenses, in pounds
otherIncomeNoOther taxable income such as a salary or pension, in pounds
businessMilesNoBusiness miles driven in a car or van, claimed at the approved mileage rate
studentLoanPlanNoStudent loan plans held: one plan or a list of every plan, e.g. ["plan2", "postgrad"]. plan1 (pre-2012), plan2 (2012 onwards), plan4 (Scotland), plan5 (2023 onwards), postgrad (postgraduate loan, repaid alongside any other plan). Omit or "none" for no loan.
taxDeductedAtSourceNoTax already paid through PAYE or CIS deductions this year
pensionContributionsNoPersonal pension contributions paid (relief at source), in pounds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / studentLoanPlan / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "none",
      +      "plan1",
      +      "plan2",
      +      "plan4",
      +      "plan5",
      +      "postgrad"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "none",
      +        "plan1",
      +        "plan2",
      +        "plan4",
      +        "plan5",
      +        "postgrad"
      +      ],
      +      "type": "string"
      +    },
      +    "maxItems": 6,
      +    "type": "array"
      +  }
      +]
    • addedInput schema / properties / studentLoanPlan / description
      Added value: +"Student loan plans held: one plan or a list of every plan, e.g. [\"plan2\", \"postgrad\"]. plan1 (pre-2012), plan2 (2012 onwards), plan4 (Scotland), plan5 (2023 onwards), postgrad (postgraduate loan, repaid alongside any other plan). Omit or \"none\" for no loan."
    • removedInput schema / properties / studentLoanPlan / enum
      Removed value: -[
      -  "none",
      -  "plan1",
      -  "plan2",
      -  "plan4",
      -  "postgrad"
      -]
    • removedInput schema / properties / studentLoanPlan / type
      Removed value: -"string"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish a safe, closed-world read, so the description's added value is real: it discloses the rate source (HMRC published rates), the tax-year grounding, and the full shape of the response (take-home, effective and marginal rates, payments on account, tailored tips). It stops short of noting limits such as accuracy caveats or whether the result is advisory only.

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 sentence front-loads the purpose before layering on outputs and the no-account note, with no filler. It is dense — the enumerated output list runs long — but every clause carries information an agent would otherwise have to infer.

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?

For an eight-parameter read-only calculator with no output schema, the description supplies what the structured data cannot: rate provenance, tax-year scope, the returned metrics, and the stateless 'no account' behaviour. Nothing essential for correct invocation is missing.

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%, so the schema already explains turnover, expenses, mileage, student loan plans and the rest. The description only echoes the two headline inputs and confirms the calculation is driven by given figures rather than stored data, adding no syntax or edge-case meaning beyond the schema. Baseline 3 applies.

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?

Names a specific verb ('Estimate') and resource ('UK income tax and Class 4 National Insurance for a sole trader') plus the exact figures it returns. The clause 'Works from the figures given, without a TapTax account' implicitly separates it from account-backed siblings like get_tax_position, so an agent can route without opening schemas.

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 sole-trader framing and 'without a TapTax account' condition imply when to reach for it (standalone what-if estimates), but no sibling is named and no exclusion is stated. An agent comparing it against calculate_take_home_pay, calculate_tax_on_multiple_incomes or compare_limited_company_and_sole_trader gets no explicit tie-breaker.

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.