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

korean-tax-calc-mcp

minimum_tax

Read-onlyIdempotent

Calculate Korean corporate minimum tax from the tax base before incentives and minimum tax rate, including SME grace-year rules, to check tax due after credits and reductions.

Instructions

Minimum tax: tax base before reductions times minimum tax rate, incl. SME grace years (최저한세). 최저한세(감면 전 과세표준 × 최저한세율). 언제: 세액감면·공제를 받은 뒤에도 납부해야 할 최저한세를 확인할 때(중소기업 졸업 유예 연차 포함). 입력: 감면 전 과세표준(원) → base_before_incentives, 사업연도(20162026) → year, 중소기업 여부 → sme, 졸업 후 경과 연차(05) → grace_year. 결과: 최저한세액, 근거(조세특례제한법 제132조제1항). Minimum corporate tax = base before incentives × minimum tax rate. 배제 순서·서식은 minimum_tax_adjustment.

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": {
      "base_before_incentives": "<base_before_incentives>",
      "year": "<year>"
    },
    "name": "minimum_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
smeNo중소기업 여부
yearYes사업연도·귀속연도(2016~2026)
grace_yearNo중소기업 졸업 후 경과 연차(0=해당 없음, 0~5)
base_before_incentivesYes금액(원)

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 this a read-only, idempotent, non-destructive, closed-world operation. The description adds value beyond them by naming the outputs (minimum tax amount plus legal basis, 조세특례제한법 제132조제1항) and by explaining the SME grace-year dimension, which the annotations do not cover.

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 definition is organized into labeled blocks (purpose, 언제, 입력, 결과) and front-loads the formula. The English closing sentence repeats the first line's formula, and the Korean/English pairing duplicates content, but no block is wasted.

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 four-parameter calculation tool with no output schema, the definition covers the inputs, the returned value, the legal basis, the year range, and the sibling that handles the adjacent concern. Nothing an agent needs in order to call it correctly appears to be missing.

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 every parameter already carries a Korean description, so the schema does most of the work. The description restates the mapping of Korean domain terms to base_before_incentives, year, sme, and grace_year, and clarifies that grace_year 0 means 'not applicable'. This helps slightly but adds little beyond the schema.

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 definition gives a precise verb-and-resource statement: it computes the minimum tax as base before incentives times the minimum tax rate, including SME grace years, and names the statutory basis. It also distinguishes itself from the sibling minimum_tax_adjustment by assigning exclusion order and forms to that tool.

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 gives an explicit trigger: use it when checking the minimum tax payable even after tax credits and deductions, including SME grace-year counts. It routes exclusion-order and form questions to minimum_tax_adjustment. It does not state when the tool is unnecessary, but the routing to the sibling is clear.

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