Skip to main content
Glama

台灣勞健保勞退試算

by io.github.supra126

月中到職／離職破月計算

calculate_prorated
Read-onlyIdempotent

計算月中到職或離職當月的破月保費。勞保/職保/勞退按日（30 日基準）；健保採官方「月底歸屬」——到職當月計整月、離職當月不計。結果僅供參考，以勞保局、健保署核發之繳款單為準，不構成法律或會計建議。

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysYes
metaYes
bracketsYes
employeeYes
employerYes
governmentYes
healthChargedYes

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the specific calculation rules (e.g., 30-day basis for labor insurance, month-end attribution for health insurance) and the non-binding disclaimer. This adds some behavioral context beyond annotations, but given the strong annotation coverage, a score of 3 is appropriate.

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 extremely concise: two sentences plus a disclaimer. Every sentence serves a purpose—first states the core function and rules, second notes the reference-only nature. 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?

Given the complexity (11 parameters, output schema exists), the description provides sufficient high-level context: what the tool calculates, the underlying rules, and the authoritative reference. The output schema handles return values, so no further detail is needed.

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 all parameters have descriptions in the schema. The tool description does not repeat parameter details but provides an overview of the calculation logic. Baseline is 3, and the description adds no per-parameter value, so score remains 3.

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 computes prorated premiums for mid-month start or end (破月保費). It specifies the insurance types covered (勞保/職保/勞退 and 健保) and the calculation rules. This distinguishes it from siblings like calculate_old_age_pension or calculate_payroll, which handle other aspects.

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: use for mid-month start/end scenarios. It includes a disclaimer that results are for reference only. However, it does not explicitly state when not to use or mention alternatives among siblings, which would raise the score to 5.

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

All 台灣勞健保勞退試算 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct calculation scenario (e.g., payroll, pension types, supplementary premiums, income tax) with no functional overlap. The descriptions clearly differentiate their purposes.

Naming Consistency5/5

All tools follow a consistent 'calculate_' prefix for computational tools and 'list_years' for enumeration, using snake_case throughout. The verb_noun pattern is uniform.

Tool Count5/5

9 tools cover the core aspects of Taiwan's labor insurance, health insurance, pension, and tax calculations without redundancy. The count is well-matched to the domain's complexity.

Completeness5/5

The set includes all major calculations required for payroll and benefits: employer/employee burdens, multiple pension options, supplementary premiums, tax withholding, prorated scenarios, and a year reference tool. No obvious gaps.

Resources