Skip to main content
Glama

台灣勞健保勞退試算

by io.github.supra126

投保單位（雇主）補充保費

calculate_employer_supplementary_premium
Read-onlyIdempotent

計算雇主端二代健保補充保費（費率 2.11%）：(每月支付薪資總額 − 受僱者當月健保投保金額總額) × 費率，無上限。結果僅供參考，以勞保局、健保署核發之繳款單為準，不構成法律或會計建議。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNo年度（西元，如 2026）。省略則使用最新可用年度；可先用 list_years 查可用年度。
roundingNo進位策略：round=四捨五入（預設）、ceil=無條件進位、aggregate-then-round=合計後分配（政府方吸收進位差）。
monthlyPaidTotalYes每月支付薪資所得總額 A，新臺幣元（含薪資、獎金、兼職、車馬費、承攬等）。
monthlyInsuredTotalYes受僱者當月健保投保金額總額 B，新臺幣元（全體受僱者投保金額合計）。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseYes
rateYes
premiumYes

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds behavioral context by stating the calculation uses a specific formula, has no upper limit, and results are for reference only (not official). This is consistent with annotations and provides additional clarity beyond the structured hints.

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 a single, well-structured sentence that includes the formula, rate, limitation, and disclaimer. Every part is essential and there is no wasted text.

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?

Given the tool's complexity (formula, parameters, caveats) and the presence of an output schema, the description covers the essential purpose, formula, and disclaimer. It could mention that the result is a numeric value, but the output schema likely handles that.

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 input schema already documents all parameters. The description does not add further parameter details but provides the overarching formula context, which is sufficient given the schema's completeness.

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 it calculates the employer supplementary premium (雇主補充保費) with a specific formula and rate (2.11%). It distinguishes itself from sibling tools like calculate_supplementary_premium by explicitly targeting employers.

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 implies usage context by stating it calculates the employer-side premium and includes a disclaimer that results are for reference only. However, it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria.

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