Skip to main content
Glama
Sign In

TapTax

by uk.co.taptax
OverviewDiscussionsAdmin

Calculate a pro rata salary

calculate_pro_rata_salary
Read-only

Work out a part-time salary from the full-time salary and the hours or days worked compared with full time, with the take-home pay on the pro rata salary for a tax year.

Input Schema

NameRequiredDescriptionDefault
taxYearNoUK tax year, e.g. "2026-27". Defaults to the current one.
actualUnitsYesHours (or days) actually worked a week, in the same unit
fullTimeUnitsYesFull-time hours (or days) a week, e.g. 37.5
fullTimeSalaryYesFull-time annual salary
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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: the tool computes both the pro rata gross figure and the resulting take-home pay, scoped to a UK tax year. It stops short of describing output structure or the effect of student loan plans and Scottish bands on the result.

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 dense sentence that leads with the core computation and appends the take-home dimension, with no filler. It is slightly run-on and could be split, but every clause carries information.

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?

With 6 parameters, full schema coverage, and no output schema, the description covers the main inputs and signals that take-home pay is returned for a chosen tax year. Adequate for an agent to call correctly; it could have mentioned that optional student loan and Scottish taxpayer flags alter the net figure.

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%, including detailed enum explanations for studentLoanPlan and unit-consistency hints for the hours fields, so the baseline is 3. The description reinforces the salary/hours/tax-year inputs but adds no meaning beyond the schema and is silent on studentLoanPlan and scottishTaxpayer.

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 uses a specific verb ('work out') and precise resource ('a part-time salary from the full-time salary and the hours or days worked compared with full time'), and additionally states it returns take-home pay for a tax year. It is clearly distinguishable from siblings like convert_salary_to_hourly_rate, but it never names or contrasts 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 Guidelines3/5

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

Usage is implied — you call it when you have a full-time salary and want the pro rata equivalent plus net pay. There is no explicit when-to-use/when-not guidance and no routing to alternatives such as calculate_take_home_pay or calculate_gross_salary_for_take_home, which overlap with the take-home component of this tool.

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

All TapTax 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