Skip to main content
Glama

Taokeh MCP server

Employer cost estimate

employer_cost_estimate
Read-only

Cost a HYPOTHETICAL hire: give a monthly wage and get back what that employee would really cost the employer each month — the wage plus employer EPF, SOCSO, EIS and the HRD Corp levy at this company's own rate — and what the employee would actually take home after employee EPF, SOCSO, EIS, SKBBK and PCB/MTD. Use it for "if I hire someone at RM4,000, what does it really cost me?" and "what would they take home?". Optional: residency (RESIDENT, the default, or NON_RESIDENT — a non-resident is taxed at a flat 30%), citizenship (MALAYSIAN or FOREIGNER — this drives the HRD Corp levy and makes SKBBK mandatory; it does NOT change the EPF, SOCSO or EIS rates applied, and it does not change tax residency, so set residency too), ageBand (UNDER_60 or 60_AND_OVER — reduced EPF and SOCSO Category 2), and epfEmployeeRate if the employee elects a reduced EPF rate. The PCB comes from Taokeh's implementation of LHDN's official computerised MTD method — the calculation IRBM confirmed in writing on 13 August 2026 (letter ref 2026-256) — not from a simplified formula. The defaults are RESIDENT, single, no children and NO TP1 reliefs, because reliefs are per-employee paperwork nobody has filled in for a person who does not exist yet; every assumption is spelled out in the reply and MUST be repeated to the user. Present it as an estimate on stated assumptions, never as a quote or as tax advice. READ-ONLY — it creates nothing, hires nobody and files nothing. ADMIN ONLY, like every payroll tool here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageBandNo
residencyNo
citizenshipNo
monthlyWageYes
epfEmployeeRateNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

The description goes well beyond the readOnlyHint annotation by stating it is READ-ONLY, creates/hires/files nothing, and is ADMIN ONLY. It discloses assumptions, defaults, that every assumption must be repeated to the user, and that the result is an estimate on stated assumptions. This is rich behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and informative, but it is a single wall of text with long parentheticals and a very specific tax-authority reference. The main purpose is front-loaded, yet structure could be improved with clearer separation of purpose, parameters, defaults, and warnings.

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?

Despite no output schema, the description clearly indicates what the tool returns and under what assumptions. It covers defaults, key optional parameters, admin/read-only behavior, and the estimate nature. The main missing piece is `epfEmployeeRate`, which prevents full completeness.

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 0%, so the description carries the burden. It explains monthlyWage, residency, citizenship, and ageBand reasonably well, but it does not explain the `epfEmployeeRate` parameter at all—its units, default, or effect. This is a notable gap for an optional parameter that an agent might need to set.

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 immediately identifies the operation: cost a HYPOTHETICAL hire from a monthly wage, returning real employer cost and employee take-home. It names the specific payroll components and gives concrete example questions, making the tool's purpose unmistakable and distinct from actual payroll or document tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It explicitly says 'Use it for...' with concrete scenarios, and it provides when-not guidance ('never as a quote or as tax advice'). It also clarifies optional inputs like residency and citizenship, including when to set both. This is strong usage direction for an agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources