Skip to main content
Glama

台灣勞健保勞退試算

by io.github.supra126

計算勞保老年一次金

calculate_old_age_lump_sum
Read-onlyIdempotent

依勞保老年一次金法定公式（平均月投保薪資 × 給付月數；年資每滿 1 年給 1 個月、逾 60 歲後之年資最多計入 5 年）試算給付金額。結果僅供參考，以勞保局、健保署核發之繳款單為準，不構成法律或會計建議。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNo年度（西元，如 2026）。省略則使用最新可用年度；可先用 list_years 查可用年度。
yearsYes保險年資：年。
monthsNo保險年資：月（0–11），預設 0。
postSixtyMonthsNo逾 60 歲以後之保險年資（月），最多計入 5 年（60 個月），超過部分不計。不得超過總保險月數。預設 0。
avgInsuredSalaryYes平均月投保薪資（最高 60 個月平均），新臺幣元。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
paymentYes
insuredMonthsCountedYes

TDQS

A3.6/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 that results are for reference only and not legal advice, but does not disclose any additional behavioral traits (e.g., no side effects, calculation-based). 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.

Conciseness5/5

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

The description is a single sentence that front-loads the formula and key constraints. It is concise with no unnecessary words or repetition.

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?

The description covers the formula, caps, and disclaimers. With an output schema present and high schema coverage, it is mostly complete. It also references list_years for year parameter guidance. A minor gap is the lack of explanation about return values, but that is covered by the output schema.

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 schema already documents all 5 parameters. The description adds the formula but does not provide additional meaning per parameter beyond what is in the schema. Baseline of 3 is appropriate.

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 defines the tool's purpose: it calculates the old-age lump sum payment using the legal formula (average monthly insured salary × number of benefit months, with specific rules for years of service and post-60 caps). It distinguishes itself from sibling tools like 'calculate_old_age_pension' by specifying the lump sum nature.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool vs. siblings. It does not mention alternatives like 'calculate_old_age_pension' or 'calculate_old_age_single_payment', leaving the agent to infer usage from the name alone.

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