Skip to main content
Glama

tax.kr_vehicle_tax

Read-onlyIdempotent

Calculates South Korea passenger vehicle annual tax and local education tax using displacement, age start date, business use, and annual payment option, with age reductions and prepayment discounts.

Instructions

한국 승용자동차 자동차세 연세액과 지방교육세(비영업용 30%)를 계산한다(지방세법 제127조, 제128조, 제151조). 배기량은 cc 정수, 차령기산일은 YYYY-MM-DD(보통 최초 신규등록일)이다. 비영업용은 차령 3년부터 연 5%, 최대 50% 경감하고 annual_payment 로 1월, 3월, 6월, 9월 연납 공제(이자율 5%)를 적용한다. 세액은 기분마다 10원 미만 버림. 승합, 화물, 특수차, 신규등록 일할계산, 조례 세율 조정은 다루지 않으며, 차령을 연식 차이로 넣으면 기산일 규칙과 어긋난다.

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>"
    },
    "name": "tax.kr_vehicle_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
as_ofNo
business_useNo
vehicle_typeNopassenger
age_start_dateNo
annual_paymentNonone
displacement_ccNo
include_proposedNo

Output Schema

NameRequiredDescriptionDefault
_metaNo서버가 붙이는 영수증(integrity), 엔진, 힌트
traceYes계산 근거(tool, formula, inputs, steps, output)
per_cc_rateNo
business_useYes
vehicle_typeYes
policy_sha256Yes
policy_sourceYes
policy_statusYes
total_payableYes
annual_paymentYes
first_half_taxYes
policy_versionYes적용된 정책 문서의 식별 정보
base_annual_taxYes
displacement_ccNo
policy_audit_idYes
second_half_taxYes
policy_citationsYes정책의 근거 조문
annual_vehicle_taxYes
local_education_taxYes
policy_effective_toYes
vehicle_tax_payableYes
policy_effective_dateYes
vehicle_age_first_halfNo
vehicle_age_second_halfNo
annual_payment_deductionYes
local_education_tax_appliesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so the description's job is to add computation semantics — and it does: 5%/yr age reduction from year 3 capped at 50%, the Jan/Mar/Jun/Sep prepayment discount at 5% interest, and truncation below 10 won per installment. It does not say what the output payload contains, but an output schema exists so that burden is already met.

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?

Single paragraph, front-loaded with the one-line purpose before rules, and every clause carries real information (statute citations, rounding rule, misuse warning). It is dense and run-on rather than structured — a bulleted split of rules vs. exclusions would scan faster — but nothing is filler.

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 calculation tool with an output schema, the description supplies the formula inputs, the reduction schedule, the rounding convention, and the exclusion list, which is close to everything an agent needs to call it correctly. The gap is the two undocumented parameters (as_of, include_proposed) plus a non-exhaustive vehicle_type value set.

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 description coverage is 0%, so the description must compensate and largely does: displacement_cc (integer cc), age_start_date (YYYY-MM-DD, usually first registration, explicitly not model-year delta), annual_payment (which months, which interest rate), and business_use (drives the 30% education tax and reduction eligibility). as_of and include_proposed are never explained, leaving two of eight parameters uninterpretable from either source.

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?

States a specific verb and resource (calculate Korean passenger-car annual vehicle tax + local education tax) plus the governing statute articles. It also enumerates the exact scope boundaries (non-business 30%, displacement, vehicle age), so an agent can distinguish this from the many other tax.* tools 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?

Explicit exclusions are given: 승합/화물/특수차, pro-rated new registration, and municipal ordinance rate adjustments are out of scope, and entering age as model-year difference is called out as a misuse. It lacks one thing for a top score — naming the alternative tool an agent should reach for when the vehicle is a van/truck or when proration is needed.

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