malaysia-payroll-mcp

Calculate EPF (KWSP) contributions

calculate_epf

Read-only

Calculates monthly EPF (KWSP) employee and employer contributions for one employee in Malaysia from fixed monthly salary, using the applicable Third Schedule band by age and citizenship.

Instructions

Works out the monthly EPF (KWSP) employee and employer contributions for one employee in Malaysia, from the EPF Third Schedule in effect for the pay period, and cites the band used. Fixed monthly salaries only.

Input Schema

Name	Required	Description
`age`	Yes	The employee's age in whole years.
`payPeriod`	No	The calendar month the salary is paid for, as YYYY-MM. It decides which rate tables apply. Defaults to the current month in Malaysia.
`citizenship`	Yes	malaysian, permanent_resident, or non_malaysian (a foreign worker without PR).
`monthlySalary`	Yes	Monthly salary in RM, at most 2 decimal places: basic pay plus fixed allowances. Excludes overtime, commission, bonuses and arrears.
`registeredWithEpfBefore1Aug1998`	No	Only for non_malaysian: true if the employee registered with EPF before 1 Aug 1998, which puts them on the Malaysian rates. Defaults to false.

Output Schema

Name	Required	Description
`part`	Yes	The EPF Third Schedule part applied.
`total`	Yes	RM
`employee`	Yes	RM, deducted from pay.
`employer`	Yes	RM, paid on top of pay.
`citations`	Yes
`payPeriod`	Yes
`disclaimer`	Yes
`explanation`	Yes
`monthlySalary`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Oct 26, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: rates come from the Third Schedule in effect for the pay period, the response cites the band used, and it is limited to fixed monthly salaries.

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?

A single front-loaded sentence that names the calculation, the governing schedule, the cited output, and the scope restriction. Nothing redundant and no filler.

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 a full output schema and 100% param coverage, the description doesn't need to explain return values, and it correctly covers source-of-truth and scope. Minor gaps: no mention of rounding/precision behavior or what happens for out-of-range or unsupported inputs.

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 every parameter including the payPeriod rate-table selection and the non_malaysian pre-1998 flag. The description adds only the salary framing ('fixed monthly salaries only'); baselining at 3 is correct here.

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?

States a specific verb and resource ('Works out the monthly EPF (KWSP) employee and employer contributions') and scopes it to one employee in Malaysia from the Third Schedule. It doesn't explicitly contrast with the sibling calculate_socso_eis, though the domain difference (EPF vs SOCSO/EIS) is obvious enough that an agent won't confuse them.

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?

'Fixed monthly salaries only' is a clear exclusion that tells the agent when not to use it (variable pay, bonuses, arrears). It stops short of naming the sibling as the tool for other statutory deductions or of stating how to handle non-fixed-income cases.

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

Deploy Server