Skip to main content
Glama

台灣勞健保勞退試算

by io.github.supra126

二代健保補充保費

calculate_supplementary_premium
Read-onlyIdempotent

計算二代健保補充保費（費率 2.11%）。bonus 課徵年度累計超過當月投保額 4 倍部分；其餘五類單次達門檻全額課（單次上限 1,000 萬）。結果僅供參考，以勞保局、健保署核發之繳款單為準，不構成法律或會計建議。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes所得類別：bonus=高額獎金、parttime=兼職薪資、professional=執行業務、dividend=股利、interest=利息、rent=租金。
yearNo年度（西元，如 2026）。省略則使用最新可用年度；可先用 list_years 查可用年度。
amountYes單次給付金額，新臺幣元。
roundingNo進位策略：round=四捨五入（預設）、ceil=無條件進位、aggregate-then-round=合計後分配（政府方吸收進位差）。
ytdBonusNo（僅 bonus）本次給付前、同雇主同年度已累計之獎金，預設 0。
monthlyInsuredSalaryNo（僅 bonus 必填）給付當月之投保金額，新臺幣元／月；門檻為其 4 倍。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rateYes
typeYes
premiumYes
chargeableYes

TDQS

A4.6/5.0
Behavior5/5

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

Annotations indicate readOnlyHint, idempotentHint, and destructiveHint=false. The description adds that the calculation uses a fixed rate of 2.11% with specific threshold and cap rules, and that the result is not binding legal advice. No contradiction with annotations.

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 few sentences covering core aspects: rate, rules for bonus vs other types, and a caveat. It is concise but could be slightly more structured by separating the rules more clearly. Still, it is efficient.

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 presence of an output schema (not shown but mentioned), return values are documented there. The description explains the input rules, thresholds, caps, and the non-binding nature. It is complete for the complexity of this calculation tool, with no missing context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with each parameter described. The description adds context beyond the schema, such as the bonus threshold being 4 times monthly insured salary and the single-payment cap of 10 million NTD. This helps the agent understand the calculation logic behind the parameters.

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 states it calculates the second-generation national health insurance supplementary premium with a specific rate of 2.11%. It lists the income types (bonus, parttime, etc.) and explains the threshold rules, clearly distinguishing it from sibling tools like calculate_employer_supplementary_premium and calculate_income_tax_withholding.

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 when to use the tool for each income type (e.g., bonus tax on excess over 4x monthly insured salary, other types tax on single amount over threshold with a cap). It states the outcome is for reference only, not legal or accounting advice. However, it does not explicitly say when not to use or compare to sibling tools.

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