Skip to main content
Glama

tax.kr_pension_income

Read-onlyIdempotent

Calculates Korean private pension withdrawal withholding, separate-taxation eligibility, and pension income deductions using private pension, deferred retirement, and non-pension withdrawals.

Instructions

한국 사적연금(연금계좌) 인출 원천징수, 분리과세 판정, 연금소득공제를 계산한다(소득세법 제129조, 제14조, 제47조의2). 금액은 원 문자열이며 private_pension_amount 는 나이별 5·4·3%(종신 3%), deferred_retirement_amount 는 이연퇴직소득으로 연금외수령 세율의 70·60·50%, non_pension_withdrawal_amount 는 연금외수령 15%. 지방소득세 10% 별도, 원 미만 절사. 사적연금 연 1,500만원 이하 분리과세. 공적연금 간이세액표 원천징수는 계산하지 않으므로 공적연금 월 원천징수액 용도로 쓰면 오용이다.

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": "tax.kr_pension_income"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNo
yearYes
as_ofNo
include_proposedNo
lifetime_annuityNo
actual_receipt_yearsNo
public_pension_amountNo0
private_pension_amountNo0
deferred_retirement_amountNo0
annual_private_pension_totalNo
deferred_retirement_tax_rateNo
non_pension_withdrawal_amountNo0

Output Schema

NameRequiredDescriptionDefault
_metaNo서버가 붙이는 영수증(integrity), 엔진, 힌트
notesYes
traceYes계산 근거(tool, formula, inputs, steps, output)
policy_sha256Yes
policy_sourceYes
policy_statusYes
policy_versionYes적용된 정책 문서의 식별 정보
policy_audit_idYes
policy_citationsYes정책의 근거 조문
withholding_totalYes
policy_effective_toYes
private_pension_taxYes
private_pension_rateYes
total_pension_amountYes
pension_income_amountYes
policy_effective_dateYes
withholding_local_taxYes
private_pension_amountYes
withholding_income_taxYes
deferred_retirement_taxYes
deferred_retirement_rateYes
pension_income_deductionYes
deferred_retirement_ratioYes
deferred_retirement_amountYes
non_pension_withdrawal_taxYes
separate_taxation_eligibleYes
non_pension_withdrawal_rateYes
separate_taxation_thresholdYes
annual_private_pension_totalYes
separate_taxation_option_taxYes
non_pension_withdrawal_amountYes

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 only declare readOnly/idempotent/closed-world, so this is a safe calculator; the description goes well beyond that by disclosing local income tax at 10% separately, truncation below one won, the 15M KRW annual separate-taxation threshold, and the 5/4/3% age-tiered rates. It omits how the two rate sources (deferred_retirement_tax_rate vs. the 70/60/50% schedule) interact when both are supplied.

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?

Front-loads the purpose, then moves to amount semantics, then rates/rounding, then exclusions — a logical order with no filler sentences. It is a single dense block, and a short labeled segmentation would make the parameter rules easier to scan, but every clause carries information.

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?

An output schema exists, so return values need not be described, and the core rate mechanics are covered. For a 12-parameter domain tool, however, roughly half the inputs have no stated meaning anywhere, which leaves an agent guessing about as_of, include_proposed, and actual_receipt_years.

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 0% across 12 parameters, so the description must carry the load. It does explain the four amount fields and the string-amount convention, plus age tiers via '나이별 5·4·3%(종신 3%)', but leaves as_of, include_proposed, actual_receipt_years, annual_private_pension_total, deferred_retirement_tax_rate and public_pension_amount's role entirely undefined.

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?

States a specific verb and resource set: '한국 사적연금(연금계좌) 인출 원천징수, 분리과세 판정, 연금소득공제를 계산한다', backed by explicit statutory articles. It also names its boundary against public-pension withholding, which cleanly separates it from payroll.kr_national_pension_benefit and tax.kr_withholding_simple.

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 negative case is explicit and concrete: using it for 공적연금 월 원천징수액 is called an 오용 (misuse). It does not name the correct alternative tool by name, nor does it spell out preconditions such as which combination of inputs to supply, so it stops short of full routing guidance.

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