Hopi

Overtime pay calculator

hopi_overtime_pay_calculator

Read-onlyIdempotent

Work out gross overtime pay from a base hourly rate and hours worked at three multipliers: standard (1x), time and a half (1.5x) and double time (2x). At least one hours figure is required. Returns pay at each rate, the total and total hours. Gross pay in GBP, before tax and NI. Source: https://hopi.co.uk/overtime-pay-calculator/

Input Schema

TableJSON Schema

Name	Required	Description
`rate`	Yes	Base hourly rate in GBP
`doubleHours`	No	Hours paid at double time, 2x (default 0)
`standardHours`	No	Hours paid at the standard rate (default 0)
`timeAndHalfHours`	No	Hours paid at time and a half, 1.5x (default 0)

Output Schema

TableJSON Schema

Name	Required	Description
`rate`	No
`summary`	Yes
`totalPay`	No
`doublePay`	No
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)
`totalHours`	No
`doubleHours`	No
`standardPay`	No
`standardHours`	No
`timeAndHalfPay`	No
`timeAndHalfHours`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026
- addedOutput schema / required
```
Added value: +[
+  "source_url",
+  "summary"
+]
```
First observedSep 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish this as a read-only, idempotent, non-destructive calculator. The description adds meaningful behavior beyond annotations: it requires at least one hours input, returns pay at each rate plus total and hours, and specifies GBP pre-tax/NI output. No contradiction 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?

The description is five short sentences, with the purpose and inputs front-loaded. Every sentence adds useful information: what it computes, the input requirement, what it returns, the currency/tax context, and a source link. No wasted words.

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 a simple calculator with a complete input schema, a read-only annotation, and an output schema, the description is fully sufficient. It covers the input constraint, output summary, currency, tax treatment, and provides a source. An agent has everything needed to invoke it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so parameters are well documented. The description adds value by clarifying that at least one hours figure must be provided despite schema defaults of 0, and by linking the three multipliers to the rate categories. This goes beyond the schema's required-field definition.

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 uses a specific verb and resource ('Work out gross overtime pay') and details the three multipliers, making the tool's function unmistakable. It also differentiates itself from sibling pay calculators by stating 'Gross pay in GBP, before tax and NI'.

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?

The description provides clear context: it is for gross overtime pay before tax/NI, and it states a key prerequisite ('At least one hours figure is required'). It does not explicitly name alternative tools or say 'use X instead', but the scope is well-defined enough for an agent to select it appropriately.

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?