Skip to main content
Glama
taylee9809

budongsan-tax

by taylee9809
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Home count for exemption

count_transfer_homes
Read-onlyIdempotent

Count homes for the one-household-one-home capital gains exemption, automatically applying statutory exclusions and special rules.

Instructions

Count homes for the one-household-one-home capital gains exemption, applying statutory exclusions automatically.

트리② — 1세대1주택 비과세 판정용 주택수 산정 (소법 §88·영 §155 특례 제외 자동 적용).

items 원소: {"종류": 주택|조합원입주권|분양권|오피스텔|다가구주택|겸용주택,
"사실상주거용": bool, "취득일": "YYYY-MM-DD"(분양권 2021 이후만 산입),
"상속특례주택"/"공동상속_소수지분"/"농어촌주택특례"/"등록임대_거주주택특례": bool,
"구획수": int·"일괄양도": bool(다가구), "주택연면적"·"주택외연면적": ㎡(겸용), "라벨": str}.

다가구주택은 구획별로 각각 1주택이 원칙이고, 구획별로 양도하지 않고 하나의 매매단위로
양도할 때만 전체가 1주택이 된다(영 §155⑮) — 일괄양도 여부가 비과세를 가르는 분기다.
겸용주택은 주택 연면적이 주택외보다 크면 전부 주택, 적거나 같으면 주택 부분만 주택이며
(영 §154③) 판정 기준은 공부가 아니라 **양도 당시 사용용도**다. 결과의 겸용주택_전부주택 참조.
중과판정 주택수(영 §167의3~11)와는 별개 — 세목·용도별 주택수 분리 원칙.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so safety is covered; the description adds the notable behavioral trait that statutory exclusions are applied automatically. It further discloses the branching logic (다가구 일괄양도, 겸용주택 면적 기준) that determines the computed result, adding real value beyond the annotations.

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 English purpose sentence is front-loaded ahead of the dense Korean specification, so the reader gets the point immediately. The subsequent detail is domain-heavy but each block (item schema, 다가구 rule, 겸용주택 rule, sibling exclusion) maps to a real decision the caller must make.

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 single-parameter read-only tool with no output schema, it covers what the input must contain and the pivotal judgment branches, and it points to the output field (겸용주택_전부주택) the caller should inspect. Return-value detail is unnecessary given there is no output schema, leaving it nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage and only a generic untyped array (additionalProperties: true), the description carries the full burden and does so richly, enumerating the item fields (종류 with its domain of value types, 사실상주거용, 취득일 with the 분양권 2021 이후만 산입 rule, the various 특례 booleans, 구획수, 주택연면적/주택외연면적). This is meaning the schema entirely lacks.

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 opening sentence gives a specific verb (count) and resource (homes) scoped to the one-household-one-home capital gains exemption, and the Korean line explicitly says it applies statutory exclusions automatically. It is clearly delineated from the heavy-tax home count covered by a sibling.

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 description states the context (1세대1주택 비과세 판정) and explicitly excludes the 중과판정 주택수 (영 §167의3~11) count, which maps to the count_heavy_homes sibling, establishing the 세목·용도별 주택수 분리 원칙. It does not, however, name specific sibling tools or spell out prerequisites for invoking this one.

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