Skip to main content
Glama
malaysia-payroll-mcp

malaysia-payroll-mcp

by davidyapcc

Calculate SOCSO, SKBBK and EIS contributions

calculate_socso_eis
Read-only

Calculate monthly SOCSO, SKBBK and EIS contributions for one Malaysian employee from PERKESO rate tables, with the row cited for each fixed-salary figure.

Instructions

Works out the monthly SOCSO (PERKESO, Act 4), SKBBK (Lindung 24 Jam) and EIS (Act 800) contributions for one employee in Malaysia, from the PERKESO tables in effect for the pay period, and cites the row used for each. Fixed monthly salaries only. Include the result's disclaimer in the answer to the user.

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": {
      "monthlySalary": "<monthlySalary>",
      "age": "<age>",
      "citizenship": "<citizenship>"
    },
    "name": "calculate_socso_eis"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesThe employee's age in whole years.
payPeriodNoThe calendar month the salary is paid for, as YYYY-MM. It decides which rate tables apply. Defaults to the current month in Malaysia.
citizenshipYesmalaysian, permanent_resident, or non_malaysian (a foreign worker without PR).
skbbkStatusNoSOCSO's 24-hour protection scheme (SKBBK, Lindung 24 Jam). Everyone is covered by default; opted_out only if PERKESO approved the employee's opt-out, which foreign workers can't do. Defaults to covered.
monthlySalaryYesMonthly salary in RM, at most 2 decimal places: basic pay plus fixed allowances. Excludes overtime, commission, bonuses and arrears.
eisPayableBefore57NoRequired for employees aged 57 to 59: true if EIS contributions were payable for them before they turned 57 (even if never paid). Can't be worked out from age.

Output Schema

NameRequiredDescriptionDefault
eisYes
skbbkYes
socsoYes
totalsYes
citationsYes
payPeriodYes
disclaimerYes
explanationYes
skbbkStatusYes
monthlySalaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses that the computation is table-driven and period-dependent, that the applicable rate row is cited per contribution, and that a disclaimer must be propagated to the user – all non-obvious traits. It does not discuss how unsupported inputs (non-fixed pay) are handled.

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?

Three tight sentences: what it computes and in what scope, the input restriction, then the output/disclaimer obligation. Every clause carries information and the main purpose is front-loaded.

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 an output schema present, return values need no explanation, and the description covers scope, the fixed-salary limit, table sourcing and the disclaimer duty. Minor gap: nothing says what happens when the pay period falls outside available tables or how partial months are treated.

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% and each parameter is already documented in detail, including the pay-period table selection and the 57-59 EIS rule. The description's only added semantic is the 'fixed monthly salaries only' qualification on the salary input, so the baseline 3 applies.

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 precise resource: monthly SOCSO, SKBBK and EIS contributions for one Malaysian employee, computed from the PERKESO tables in force for the pay period. The statutory domain makes it naturally distinct from calculate_mtd/calculate_epf/calculate_net_pay, though it never names 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?

'Fixed monthly salaries only' is a genuine exclusion that tells the agent when not to reach for this tool, and the disclaimer instruction shapes how results are surfaced. However, there is no routing guidance toward the sibling calculators (e.g. use calculate_net_pay for take-home pay), so the agent must infer the boundary itself.

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