Skip to main content
Glama

payroll.kr_health_income_premium

Read-onlyIdempotent

Calculates Korean workplace health insurance premiums on non-wage income, long-term care premiums, and annual wage-based settlement differences, including whether installment payment applies.

Instructions

건강보험 직장가입자의 보수 외 소득월액보험료(국민건강보험법 제71조: 연 2천만원 초과분의 1/12, 근로·연금소득 50% 평가, 이자·배당 1천만원 이하 제외, 월 상한 4,591,740원)와 장기요양보험료, 보수총액 기준 보수월액보험료 연간 정산 차액과 분할납부 가능 여부를 계산한다. 소득은 소득 종류별 연간 소득금액(원 문자열), year 는 부과 또는 보수 귀속 연도, 원 미만 버림. 지역가입자 보험료 계산에 쓰면 오용이다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>"
    },
    "name": "payroll.kr_health_income_premium"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
as_ofNo
end_monthNo
start_monthNo
wage_incomeNo0
other_incomeNo0
pension_incomeNo0
business_incomeNo0
dividend_incomeNo0
interest_incomeNo0
include_proposedNo
ltc_premium_paidNo
health_premium_paidNo
annual_remuneration_totalNo

Output Schema

NameRequiredDescriptionDefault
_metaNo서버가 붙이는 영수증(integrity), 엔진, 힌트
traceYes계산 근거(tool, formula, inputs, steps, output)
settlementNo
policy_sha256Yes
policy_sourceYes
policy_statusYes
income_premiumYes
policy_versionYes적용된 정책 문서의 식별 정보
policy_audit_idYes
policy_citationsYes정책의 근거 조문
policy_effective_toYes
policy_effective_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so the description is free to add substantive behavior: the legal basis (국민건강보험법 제71조), the 2천만원 threshold with 1/12 proration, 50% evaluation of 근로·연금소득, the 이자·배당 1천만원 exclusion, the 4,591,740원 monthly cap, and 원 미만 버림 rounding. It stops short of describing the settlement comparison logic or what the response contains, but the output schema covers returns.

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?

Two sentences: one dense but front-loaded calculation sentence with parenthetical rules, one short misuse warning. Every clause (thresholds, cap, rounding) carries decision-relevant information, though the parenthetical stack makes it harder to scan than a bulleted rule list would be.

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?

For a 14-parameter tool with zero schema descriptions, the description leaves too much undefined — particularly annual_remuneration_total and the two *_premium_paid inputs that drive the annual settlement, and the include_proposed flag. An agent can call it with just year, but cannot confidently populate the settlement or month-range parameters from this text alone.

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 0%, so the description must carry parameter meaning, and it does clarify two clusters: income parameters are annual income amounts by type as won-denominated strings, and year is the imposition or remuneration attribution year. However, seven parameters (as_of, start_month, end_month, include_proposed, ltc_premium_paid, health_premium_paid, annual_remuneration_total) get no explanation at all, leaving the settlement and proration inputs undocumented.

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 names a specific verb (계산한다) and enumerates exactly what is computed: 보수 외 소득월액보험료, 장기요양보험료, 보수월액보험료 연간 정산 차액, and 분할납부 가능 여부. No sibling tool in the list covers Korean health-insurance premium computation, and the closing misuse note (지역가입자 보험료) further fences the scope.

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?

It gives an explicit when-not: "지역가입자 보험료 계산에 쓰면 오용이다", which steers an agent away from the wrong subscriber class. It does not name an alternative tool for that case, and the positive trigger (직장가입자 with 보수 외 소득) is implied by the scope statement rather than stated as a rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools