Skip to main content
Glama
supra126

taiwan-payroll

計算台灣勞健保勞退

calculate_payroll

Compute Taiwan monthly payroll costs for labor insurance, health insurance, labor pension, and occupational accident contributions. Supports different worker types, dependents, and part-time status.

Instructions

計算台灣某月薪資的勞保(含就保)、健保、勞退、職災各方(員工/雇主/政府)負擔。支援不同身份別、眷屬、自提、部分工時。結果僅供參考,以勞保局、健保署核發之繳款單為準,不構成法律或會計建議。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNo年度(西元,如 2026)。省略則使用最新可用年度;可先用 list_years 查可用年度。
monthlySalaryYes月薪資總額(經常性薪資),新臺幣元/月。
identityNo身份別(預設 category1):category1=本國勞工或外籍配偶;migrantGeneral=一般移工(勞保僅普通事故 11.5%、無就保/勞退);migrantDomestic=家事移工(僅健保+職災,職災費率請以 occupationalRate 傳 0.0018)。不適用的險種回傳 0。
dependentsNo健保眷屬人數(計費上限 3 口),預設 0。
employmentInsuranceNo是否參加就業保險(勞保費率 12.5% 或 11.5%),預設 true。一般移工/家事移工一律視為不參加。
pensionSelfContributionNo勞工自願提繳率,小數(0~0.06,如 0.06 表 6%),預設 0。
occupationalRateNo職災行業別費率,小數比例(如 0.0021 表 0.21%;家事移工 0.0018),範圍 [0, 0.02)。省略則用該年度平均費率。
partTimeNo是否為部分工時:true 時未達基本工資者勞保/健保對到官方低級距(職保仍歸第 1 級)。預設 false。
roundingNo進位策略:round=四捨五入(預設)、ceil=無條件進位、aggregate-then-round=合計後分配(政府方吸收進位差)。
Behavior3/5

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

With no annotations, the description includes a disclaimer that results are for reference and subject to official documents, which is valuable. However, it does not describe output format, rate updates, or any limitations beyond the disclaimer.

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

Conciseness4/5

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

The description is a single concise paragraph that front-loads the main purpose and lists supported features. It is appropriately sized but could benefit from structured bullet points for better readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 9 parameters and no output schema, the description lacks information about return structure (e.g., breakdown by party), error handling, or frequency of rate updates. This is a significant gap for a complex tool.

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 coverage is 100% with detailed descriptions for each parameter. The tool description adds no additional parameter context beyond the schema, so it meets the baseline.

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 clearly states the tool calculates Taiwan's payroll deductions (labor insurance, health insurance, pension, occupational accident) for all parties. It specifies supported variations (identity, dependents, etc.) and distinguishes itself from sibling tools like calculate_old_age_pension by its comprehensive scope.

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?

The description implies usage for full payroll calculation but does not explicitly state when to use this tool versus siblings like calculate_income_tax_withholding or calculate_old_age_pension. No when-not-to-use or alternative recommendations are given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/supra126/taiwan-payroll'

If you have feedback or need assistance with the MCP directory API, please join our Discord server