Hopi

Redundancy pay calculator

hopi_redundancy_pay_calculator

Read-onlyIdempotent

Work out UK statutory redundancy pay for redundancies on or after 6 April 2026, using the gov.uk count-back method: for each full year of service (up to 20), 1.5 weeks if worked aged 41+, 1 week aged 22 to 40, and 0.5 weeks under 22. Weekly pay is capped at £751 and the total at £22,530. At least 2 full years of service are needed. Amounts in GBP. Source: https://hopi.co.uk/redundancy-pay-calculator/

Input Schema

TableJSON Schema

Name	Required	Description
`age`	Yes	Age at redundancy (15 to 100)
`years`	Yes	Full years of continuous service (0 to 60, cannot exceed age)
`weeklyPay`	Yes	Gross weekly pay in GBP

Output Schema

TableJSON Schema

Name	Required	Description
`age`	Yes
`total`	Yes
`weeks`	Yes
`years`	Yes
`summary`	Yes
`weeklyPay`	Yes
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)
`totalCapped`	No
`serviceCapped`	No
`cappedWeeklyPay`	No
`weeklyPayCapped`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

addedOutput schema / required

Added value: +[
+  "age",
+  "source_url",
+  "summary",
+  "total",
+  "weeklyPay",
+  "weeks",
+  "years"
+]

First observedSep 20, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already mark it as read-only and idempotent, and the description goes well beyond that by exposing the full statutory count-back formula, age bands, weekly pay cap, total cap, and eligibility condition. No contradictions with annotations.

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?

Four compact sentences pack purpose, legal basis, computation, caps, eligibility, currency, and source with no filler. The main verb and object are front-loaded, and every remaining clause carries operational value.

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?

The definition is complete for an agent to decide and invoke the tool: it gives the effective-dated rules, the exact multiplier table, caps, and the minimum service threshold. Since an output schema exists, not describing the return shape is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Though schema coverage is 100%, the description adds critical meaning: years are capped at 20 for the calculation, weeklyPay is capped at £751, the total at £22,530, and the age bands map directly to the age parameter. These nuances are not inferable from the schema alone.

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 opens with a specific verb ('Work out') and a precise resource ('UK statutory redundancy pay'), and adds a clear effective date. This is unambiguous and distinct from any sibling calculator, which all concern other domains.

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 states when the tool applies ('redundancies on or after 6 April 2026') and imposes an eligibility threshold ('At least 2 full years of service are needed'), which tells an agent not to use it for earlier or shorter-service cases. It does not explicitly name alternative calculators, but no sibling covers the same domain.

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

All Hopi tools Inspect

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

Need Help?