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

korean-tax-calc-mcp

dominant_shareholder

Read-onlyIdempotent

Determine who is the controlling shareholder of a beneficiary corporation for intra-group transfer gift tax by analyzing direct stakes, kinship ties, and the fiscal year-end date.

Instructions

Controlling shareholder test for beneficiary corporation in intra-group transfer gift tax (지배주주 판정). 수혜법인의 지배주주 판정(상증법 시행령 제34조의3제1항). 언제: 일감몰아주기 증여의제이익 계산에서 수혜법인의 지배주주가 누구인지 판정할 때. 입력: 수혜법인(이름) → corp, people={이름: {구분: "개인"|"법인"}} → people, family=[[a, b, "부모자녀"|"배우자"]] → family, stakes=[[보유자, 법인, 지분율(0~1)]] → stakes(related_judge와 동일 형식). 기준일: 수혜법인 사업연도 종료일 → on. 최대주주등을 묶는 친족 범위가 2023.2.28.까지 6촌 혈족·4촌 인척, 2023.3.1.부터 4촌 혈족·3촌 인척(국세기본법 시행령 제1조의2제1항). 결과: 지배주주(이름)·판정 이유·친족 범위. 수혜법인의 지배주주를 판정한다(중견기업 중 직접보유 최고자 / 법인이면 직접+간접 최고 개인).

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": {
      "corp": "<corp>",
      "people": "<people>",
      "family": "<family>",
      "stakes": "<stakes>"
    },
    "name": "dominant_shareholder"
  }
}

Input Schema

NameRequiredDescriptionDefault
onNo판정 기준일 = 수혜법인 사업연도 종료일(YYYY-MM-DD). 친족 범위가 2023.2.28.까지 6촌 혈족·4촌 인척, 2023.3.1.부터 4촌·3촌. 생략하면 현행 범위
corpYes수혜법인(이름)
familyYes친족 관계 [[a, b, "부모자녀"|"배우자"]]. 예: [["김갑", "김을", "부모자녀"]]
peopleYes사람·법인 목록 {이름: {"구분": "개인"|"법인"}}. 예: {"김갑": {"구분": "개인"}}
stakesYes직접보유비율 [[보유자, 법인, 지분율(0~1)]]. 예: [["김갑", "㈜대한", 0.30]]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.37.0
    • addedInput schema / properties / on
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "판정 기준일 = 수혜법인 사업연도 종료일(YYYY-MM-DD). 친족 범위가 2023.2.28.까지 6촌 혈족·4촌 인척, 2023.3.1.부터 4촌·3촌. 생략하면 현행 범위",
      +  "title": "On"
      +}
  2. First observedv0.9.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine substance beyond that: the judgement rule (직접보유 최고자, or 직접+간접 최고 개인 for corporate holders) and the date-dependent kin scope, which changes at 2023.2.28/2023.3.1. It does not cover edge behavior such as what happens when no dominant shareholder is found or when stake data is incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but content is duplicated across an English headline and a Korean purpose sentence, and the closing sentence restates the purpose again ('수혜법인의 지배주주를 판정한다'). The input/criteria/result structure is helpful, yet trimming the redundant restatements would sharpen it.

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 five-parameter tool with nested objects and a date-sensitive statutory rule, the description covers inputs, the reference date, the judgement criteria, and the returned items (지배주주, 판정 이유, 친족 범위). No output schema exists, so it correctly states what comes back; only edge-case and failure behavior is missing.

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 coverage is 100%, so the baseline is 3, but the description adds meaning: it maps each input to a param (corp, people, family, stakes), notes stakes is 직접보유비율 in 0~1 and uses the same format as related_judge, and explains that 'on' is the fiscal year-end date driving the kin-scope rule. That is real value beyond the schema text.

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?

Names a specific verb and resource ('수혜법인의 지배주주를 판정한다') and anchors it in the legal provision (상증법 시행령 제34조의3제1항) plus the computation it feeds (일감몰아주기 증여의제이익). It is clearly distinct in domain from the nearest sibling, stock_major_shareholder, but never names or contrasts an alternative explicitly, which keeps it just below 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?

The '언제:' line states the use case precisely: determine who the controlling shareholder of the beneficiary corporation is within the deemed-gift profit calculation. There is no when-not guidance or explicit routing to a sibling, so it stops short of 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