Skip to main content
Glama

tax.capital_gains_kr

Read-onlyIdempotent

Calculate Korean capital gains tax for property transfers by applying exemptions, deductions, high-value housing apportionment, and applicable surcharge rates.

Instructions

한국 양도소득세를 계산한다(소득세법 제89조·제95조·제103조·제104조). 금액은 원 단위 Decimal 문자열, 보유·거주 기간은 만 년 정수다. 1세대1주택 비과세와 12억 초과 고가주택 안분, 장기보유특별공제(표 1, 보유·거주 표 2), 기본공제 250만원, 단기보유·분양권·비사업용 토지·미등기·조정대상지역 다주택 중과 세율 중 해당 경로의 큰 세액을 적용한다. 세액은 decimals(기본 0)자리 HALF_UP 이고 지방소득세는 포함하지 않는다. 보유 2년 이상 다주택 중과 제외 판정에는 transfer_date 가 필요하다.

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": {
      "acquisition_price": "<acquisition_price>",
      "sale_price": "<sale_price>",
      "holding_years": "<holding_years>",
      "is_one_house": "<is_one_house>",
      "year": "<year>"
    },
    "name": "tax.capital_gains_kr"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
as_ofNo
decimalsNo
asset_typeNo
sale_priceYes
is_one_houseYes
holding_yearsYes
transfer_dateNo
is_unregisteredNo
residence_yearsNo
include_proposedNo
acquisition_priceYes
is_non_business_landNo
apply_basic_deductionNo
multi_house_surchargeNonone
acquired_in_regulated_areaNo

Output Schema

NameRequiredDescriptionDefault
taxYes
gainYes
_metaNo서버가 붙이는 영수증(integrity), 엔진, 힌트
traceYes계산 근거(tool, formula, inputs, steps, output)
exemptYes
tax_baseYes
ltct_rateYes
applied_rateYes
taxable_gainYes
policy_sha256Yes
policy_sourceYes
policy_statusYes
ltct_deductionYes
policy_versionYes적용된 정책 문서의 식별 정보
basic_deductionYes
policy_audit_idYes
rate_candidatesYes
policy_citationsYes정책의 근거 조문
policy_effective_toYes
taxable_portion_gainYes
policy_effective_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior4/5

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

With readOnly/idempotent already declared, the description still adds meaningful behavior: amounts are Decimal strings in won, periods are whole-year integers, rounding is HALF_UP at `decimals` (default 0), and local income tax is explicitly excluded from the result. That last clause is a genuinely useful scope caveat. It does not describe failure modes or validation behavior (e.g., what happens with missing transfer_date).

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?

Dense but front-loaded: the core action and legal basis come first, then input conventions, then the tax-path enumeration, then rounding/output caveat. No filler sentences, though the long enumeration clause is harder to parse than it needs to 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?

Output schema exists, so return values needn't be described, and the safety profile is covered by annotations. But for a 16-parameter, high-complexity statutory calculator, several optional parameters (as_of, asset_type, include_proposed, year) are undocumented in both schema and description, leaving real ambiguity about how to configure a correct call.

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% across 16 parameters, so the description must compensate. It does explain the units/conventions for the price and period fields, the role of decimals, the basic deduction of 2.5M KRW (apply_basic_deduction), residence_years (표 2), and the transfer_date dependency, but leaves as_of, asset_type, year semantics, and include_proposed entirely unexplained.

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?

States a specific verb+resource ('한국 양도소득세를 계산한다') and anchors it with the governing statute articles (제89조·제95조·제103조·제104조), which makes the scope unambiguous. It does not, however, name or distinguish itself from lookalike siblings such as realestate.kr_transfer_tax or tax.kr_comprehensive_income_tax, so sibling differentiation is left to inference.

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 implies when it applies by enumerating the tax paths it handles (1세대1주택 비과세, 고가주택 안분, 중과세율, 분양권, 비사업용 토지, 미등기) and flags that transfer_date is required for the multi-house surcharge exclusion test. It gives no explicit when-to-use/when-not guidance and never directs the agent to an alternative tool.

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