Skip to main content
Glama
supra126

taiwan-payroll

投保單位(雇主)補充保費

calculate_employer_supplementary_premium

Calculates employer supplementary premium for second-generation National Health Insurance (2.11% rate) using monthly salary total minus insured amount total. Results are for reference only.

Instructions

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

Input Schema

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

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

No annotations are provided, so the description carries full burden. It discloses the calculation formula, rate, and caveat that results are for reference only. However, it does not explicitly state that the tool is read-only or describe any side effects, permissions, or error handling beyond the formula.

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 two sentences, concise and front-loaded with the key formula and rate. Every word contributes essential information without redundancy.

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 has 4 parameters, no output schema, and moderate complexity, the description is nearly complete. It explains the formula, rate, rounding options, and caveat. It is missing explicit info on the return value format (presumably a number), but the use case makes it obvious.

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%, with detailed parameter descriptions. The description adds context like '無上限' and the formula, but the schema already explains the parameters well. The description provides additional value by explaining the rounding strategies and the reference-only nature.

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 title and description explicitly state the tool calculates employer supplementary premium for National Health Insurance with the formula, rate (2.11%), and no cap. It clearly distinguishes from siblings like 'calculate_supplementary_premium' (likely for employees) and other calculation tools.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool vs. alternatives like 'calculate_supplementary_premium' or other payroll tools. While the name and formula imply it's for employer premiums, there is no direct guidance on selection criteria or when not to use it.

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