Skip to main content
Glama
korean-tax-calc-mcp

korean-tax-calc-mcp

inheritance_tax

Read-onlyIdempotent

Calculate Korean inheritance tax by deriving taxable estate value, deductions, tax base, calculated tax, and final payable amount for filing or planning.

Instructions

Inheritance tax: taxable value, deductions, tax base, calculated tax and tax payable (상속세). 거주자 피상속인 상속세 과세가액·상속공제·과세표준·산출세액·납부할세액. 언제: 상속세 신고·계산 시. 입력: 본래 상속재산가액 → estate_value, 상속개시연도 → year, 간주상속재산 → deemed_estate, 추정상속재산 목록 → presumed_items, 비과세·불산입·공과금·장례비용·봉안비용·채무·사전증여·특별공제 등. spouse.legal_share는 '3/5' 같은 분수 문자열 또는 0.6 같은 0 초과 1 이하 소수. 신고: 법정신고기한 안 신고 → filed=true(신고세액공제). 기한 뒤 신고 → filed=false, late_filed_on=기한후신고일 — 2020.1.1. 이후 기한후신고면 인적공제 합계와 일괄공제 5억원 중 큰 금액(제21조제1항, 법률 제16846호 부칙 제5조 — 상속개시일이 아니라 신고일 기준), 신고세액공제 없음. 무신고(late_filed_on 비움)면 일괄공제 5억원. 결과: 과세가액·상속공제합계·과세표준·산출세액·신고세액공제·납부할세액, 공제 내역, 근거. 상속세 과세가액·공제·세액 계산.

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>",
      "estate_value": "<estate_value>"
    },
    "name": "inheritance_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes사업연도·귀속연도(2016~2026)
debtsNo금액(원)
filedNo법정신고기한 내 신고
minorsNo[미성년자별 19세까지 남은 연수]
spouseNo실제 상속받은 금액·법정상속분 등. {actual(실제 상속액), legal_share('3/5' 같은 분수 문자열 또는 0.6 같은 0 초과 1 이하 소수), prior_gift_tax_base(선택 — 가산한 증여재산 중 배우자가 사전증여받은 재산의 증여세 과세표준, 한도식에서 뺌)}
seniorsNo65세 이상 인원
childrenNo자녀 수
disabledNo[장애인별 기대여명 연수]
excludedNo금액(원)
nontaxableNo금액(원)
estate_valueYes금액(원)
funeral_costNo금액(원)
appraisal_feeNo금액(원)
deemed_estateNo금액(원)
late_filed_onNo기한후신고일(YYYY-MM-DD, filed=false일 때만). 2020.1.1. 이후 기한후신고면 인적공제 합계와 일괄공제 5억원 중 큰 금액(법률 제16846호 부칙 제5조), 비우면 무신고로 보고 5억원
other_creditsNo금액(원)
presumed_itemsNo[{kind, window, amount, unexplained}]
public_chargesNo금액(원)
gift_tax_creditNo금액(원)
cohabiting_houseNo{value, secured_debt?}
sole_spouse_heirNo배우자 단독상속
enshrinement_costNo금액(원)
prior_gifts_heirsNo금액(원)
renounced_to_nextNo금액(원)
prior_gifts_othersNo금액(원)
share_appraisal_feeNo금액(원)
bequest_to_non_heirsNo금액(원)
net_financial_assetsNo금액(원)
prior_gift_deductionsNo금액(원)
share_appraisal_countNo평가기관 수
business_farm_deductionNo금액(원)
generation_skip_surchargeNo금액(원)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.57.1
    • changedInput schema / properties / spouse / description
      Previous value: -"실제 상속받은 금액·법정상속분 등. {actual(실제 상속액), legal_share('3/5' 같은 분수 문자열 또는 0.6 같은 0 초과 1 이하 소수)}"New value: +"실제 상속받은 금액·법정상속분 등. {actual(실제 상속액), legal_share('3/5' 같은 분수 문자열 또는 0.6 같은 0 초과 1 이하 소수), prior_gift_tax_base(선택 — 가산한 증여재산 중 배우자가 사전증여받은 재산의 증여세 과세표준, 한도식에서 뺌)}"
  2. Changed1 schema field changedv0.51.0
    • addedInput schema / properties / late_filed_on
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "기한후신고일(YYYY-MM-DD, filed=false일 때만). 2020.1.1. 이후 기한후신고면 인적공제 합계와 일괄공제 5억원 중 큰 금액(법률 제16846호 부칙 제5조), 비우면 무신고로 보고 5억원",
      +  "title": "Late Filed On"
      +}
  3. Changed1 schema field changedv0.11.0
    • changedInput schema / properties / spouse / description
      Previous value: -"실제 상속받은 금액·법정상속분 등"New value: +"실제 상속받은 금액·법정상속분 등. {actual(실제 상속액), legal_share('3/5' 같은 분수 문자열 또는 0.6 같은 0 초과 1 이하 소수)}"
  4. Addedv0.10.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds real substance beyond them: the filed=true vs filed=false vs late_filed_on-omitted branches, the fact that the 2020.1.1 rule keys off the filing date rather than the death date, that late filing forfeits the filing credit, and the statutory basis (법률 제16846호 부칙 제5조). It does not cover error/validation behavior or what happens with inconsistent inputs, so not a 5.

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-loaded with purpose, then when-to-use, then input mapping, then filing edge cases, then results — a sensible order for a 32-parameter tool, and the density is defensible at this complexity. There is some waste: the trailing sentence "상속세 과세가액·공제·세액 계산" merely repeats the opening, and the spouse.legal_share sentence duplicates the schema text.

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?

For a 32-parameter, no-output-schema tool, the description covers purpose, trigger context, the highest-risk edge cases (filing timing and its effect on deductions and credits), and enumerates the return fields so the agent knows what comes back. The remaining gap is that most individual deduction/credit parameters are left entirely to the schema, which is acceptable only because schema coverage is 100%.

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%, so the baseline is 3. The description adds a Korean-to-parameter mapping (본래 상속재산가액→estate_value, 상속개시연도→year, 간주상속재산→deemed_estate, 추정상속재산 목록→presumed_items), which is useful, but the spouse.legal_share format and the late_filed_on rule are restated nearly verbatim from the schema rather than extending it. Roughly half of the 32 parameters (minors, seniors, disabled, cohabiting_house, business_farm_deduction, generation_skip_surcharge, etc.) get no treatment in the description at all.

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 opening line names the resource (inheritance tax, 상속세) and enumerates the exact outputs computed: taxable value, deductions, tax base, calculated tax, tax payable. It is unambiguous what the tool produces. It stops short of naming a sibling (e.g. gift_tax or inheritance_gift_valuation) to route away from, so it does not fully earn a 5.

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?

"언제: 상속세 신고·계산 시" gives a clear triggering context — use it when filing or computing an inheritance tax return. There are no explicit exclusions or pointers to alternative tools for adjacent cases such as gift tax or valuation, which keeps it below a 5.

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