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

korean-tax-calc-mcp

kinship_check

Read-onlyIdempotent

Check the kinship degree between two people and determine whether their relationship falls within Korean tax-law family scope on a specified date.

Instructions

Kinship degree check between two individuals and family scope for tax purposes (친족관계). 두 개인의 친족관계(혈족·인척 촌수, 배우자)와 기준일 친족 범위 해당 여부. 언제: 두 사람이 친족인지, 국세기본법·상증법상 친족 범위에 들어가는지 확인할 때. 입력: 당사자 a(이름) → a, 당사자 b(이름) → b, 기준일(YYYY-MM-DD) → on, family=[[a, b, "부모자녀"|"배우자"]] → family(related_judge와 동일 형식). 결과: 관계(촌수·배우자)·기준일·친족 범위·국기법 친족 여부·상증법 친족(사돈 포함) 여부. 두 개인의 친족관계(혈족·인척 촌수, 배우자)와 기준일 친족 범위 해당 여부를 확인한다.

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": {
      "a": "<a>",
      "b": "<b>",
      "on": "<on>",
      "family": "<family>"
    },
    "name": "kinship_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYes당사자 a(이름)
bYes당사자 b(이름)
onYes기준일 YYYY-MM-DD
familyYes친족 관계 목록 [[a, b, "부모자녀"|"배우자"]]. 예: [["김갑", "김을", "부모자녀"]] — related_judge와 동일 형식

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered. The description adds what the annotations cannot: the returned judgment axes (촌수, 기준일, 친족 범위, 국기법 친족, 상증법 친족 including 사돈). It does not disclose any failure modes, e.g. what happens when the family list is incomplete or a name is unknown.

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?

The 언제/입력/결과 labelling front-loads purpose and makes the block scannable. The final sentence repeats the opening definition almost verbatim (친족관계·촌수·배우자·기준일 친족 범위), which is pure redundancy, and the bilingual duplication lengthens an otherwise tight definition.

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?

There is no output schema, and the description compensates by enumerating the result fields, which is exactly what an agent needs to interpret the response. For a 4-required-parameter, fully covered schema the definition is close to self-sufficient; the only gap is guidance on incomplete kinship evidence.

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 100% and the schema descriptions already carry the a/b/on/family meanings, plus the [["김갑","김을","부모자녀"]] example. The description's 입력 block restates the same parameter-to-field mapping with no additional constraints (no ordering rule, no note on whether family must contain the queried pair), so baseline 3 applies.

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 operation (kinship degree between two individuals) plus the second output dimension (whether the pair falls inside statutory kinship scope under 국세기본법/상증법). It also names the exact relationship concepts returned (혈족·인척 촌수, 배우자), which no sibling tool covers, so an agent can identify it without opening the schema.

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 언제 (when) clause gives an explicit trigger: confirming whether two people are kin or fall inside the tax-law kinship perimeter. It also references related_judge as sharing the same family-format contract, which helps picking between them, but it never states when to prefer related_judge over this tool or what the boundary is.

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