Skip to main content
Glama

Work out the salary for a take-home figure

calculate_gross_salary_for_take_home
Read-only

Work out the gross UK salary needed to take home a given amount a year after income tax, employee National Insurance, student loan and a pension percentage, for a tax year (net to gross).

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": {
      "targetTakeHome": "<targetTakeHome>"
    },
    "name": "calculate_gross_salary_for_take_home"
  }
}

Input Schema

NameRequiredDescriptionDefault
taxYearNoUK tax year, e.g. "2026-27". Defaults to the current one.
pensionPercentNoEmployee pension as a percentage of gross, e.g. 5
targetTakeHomeYesTake-home pay wanted a year, in pounds
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.
scottishTaxpayerNoTrue for a Scottish taxpayer (Scottish bands)

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"
      +  }
      +]
    • changedInput schema / properties / studentLoanPlan / description
      Previous value: -"Student loan plan, if any (plan4 is Scotland, postgrad the postgraduate loan)"New 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. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already cover read-only, non-destructive, and closed-world behavior. The description adds meaningful domain context by identifying income tax, employee National Insurance, student loan, pension percentage, and UK tax year as calculation inputs, though it does not state rounding or other calculation assumptions.

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 front-loaded sentence with no redundant restatement of the tool name. It is dense but readable and every clause contributes to explaining the calculation.

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 five-parameter calculator with full schema coverage and read-only annotations, the description supplies the key domain context and direction of calculation. Minor gaps around return precision and Scottish taxpayer handling are adequately covered by the schema and title.

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 documents all five parameters, including enums and ranges. The description reinforces the target take-home amount and named deductions but adds no parameter-level detail beyond what the schema provides.

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 states a specific verb and resource ('work out the gross UK salary') and defines the scope precisely as a net-to-gross calculation after named deductions. The parenthetical '(net to gross)' distinguishes it from gross-to-net sibling tools such as calculate_take_home_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?

It makes clear to use this when the desired annual take-home amount is known and the required gross salary is needed, in a UK tax-year context. It does not explicitly name the alternative calculate_take_home_pay or state exclusions, so it falls short of a 5.

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.