Skip to main content
Glama

台灣勞健保勞退試算

by io.github.supra126

薪資所得扣繳稅額

calculate_income_tax_withholding
Read-onlyIdempotent

計算薪資所得扣繳稅額：居住者固定月薪(公式法)、非每月給付獎金(5%，未達起扣標準免扣)、非居住者(18%；月薪≤1.5倍基本工資為6%)。結果僅供參考，以勞保局、健保署核發之繳款單為準，不構成法律或會計建議。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes扣繳類型：resident=居住者固定月薪(公式法)、residentBonus=居住者非每月給付(獎金)5%、nonResident=非居住者18%/6%。
yearNo年度（西元，如 2026）。省略則使用最新可用年度；可先用 list_years 查可用年度。
amountNo該筆給付金額，新臺幣元（僅 residentBonus）。
dependentsNo配偶及受扶養親屬人數（僅 resident），預設 0。
monthlySalaryNo月薪資，新臺幣元（resident／nonResident 用）。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rateYes
withholdingYes
taxableAnnualNo

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds meaningful caveats that results are for reference only and not legally binding, enhancing transparency about limitations and official reliance.

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 paragraph that efficiently conveys all essential information without redundancy. Each sentence adds necessary detail, covering all three cases and the disclaimer.

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 (5 parameters, 1 required, output schema present), the description adequately explains input usage and calculation methods. It omits details about the output format, but the presence of an output schema mitigates this gap. The disclaimer about reference-only results adds necessary 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 covers 100% of parameters with descriptions. The description adds value by explaining the calculation rules behind the enum values (e.g., formula for resident, 5% threshold for bonuses, 18%/6% for non-resident) and specifying when each parameter applies, going beyond the schema.

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 the tool computes income tax withholding (薪資所得扣繳稅額) and enumerates three specific categories (resident monthly salary, resident bonus, non-resident). It distinguishes itself from sibling tools like pension calculations or supplementary premium calculators by focusing solely on 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 clear context for when to use each type (resident, residentBonus, nonResident) including rate details and conditions. However, it does not explicitly mention when not to use this tool or suggest alternatives, slightly limiting the guidance.

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