Skip to main content
Glama
supra126

taiwan-payroll

計算勞保老年一次金

calculate_old_age_lump_sum

Compute the old-age lump sum benefit under Taiwan's Labor Insurance using the legal formula: average monthly insured salary multiplied by payment months (1 month per year, up to 5 years after age 60).

Instructions

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

Input Schema

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

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

No annotations provided. Description only includes a disclaimer about reference and no legal advice. Does not disclose side effects, authentication needs, or data fetching behavior.

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?

One concise paragraph with formula upfront. No unnecessary words.

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

Completeness3/5

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

Covers the calculation logic but lacks output format description and error conditions. For a 5-parameter calculation tool, this is adequate but not fully comprehensive.

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%, so baseline is 3. Description adds minimal context beyond the formula (e.g., postSixtyMonths limit) but doesn't significantly enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies it calculates the old-age lump sum benefit using the legal formula. However, it does not explicitly differentiate from sibling tools like calculate_old_age_pension or calculate_old_age_single_payment.

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?

No guidance on when to use this tool versus alternatives. No prerequisites or exclusions provided. Only a disclaimer that results are for reference.

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