Skip to main content
Glama

tax.kr_education_tax_add

Read-onlyIdempotent

Calculate Korean local education tax by multiplying a base tax amount by the applicable rate, with configurable rounding and decimals; set the correct rate per base tax.

Instructions

한국 지방교육세를 본세 x 부가세율로 계산한다(지방세법 제151조). base_tax 는 재산세·취득세·등록면허세 등 본세액(원, 0 이상 Decimal 문자열), rate 기본 0.20(0 이상 1 이하), rounding 기본 DOWN, decimals 기본 0이라 원 미만을 버린다. 본세마다 세율이 다르므로 rate 를 확인하지 않고 기본값을 쓰면 틀릴 수 있다.

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_tax": "<base_tax>"
    },
    "name": "tax.kr_education_tax_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateNo0.20
base_taxYes
decimalsNo
roundingNoDOWN

Output Schema

NameRequiredDescriptionDefault
rateYes
_metaNo서버가 붙이는 영수증(integrity), 엔진, 힌트
traceYes계산 근거(tool, formula, inputs, steps, output)
base_taxYes
education_taxYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, so the description correctly spends its words elsewhere: rounding default DOWN truncates sub-won amounts, decimals default 0, rate bounds 0–1, base_tax must be a non-negative Decimal string. It does not describe the response shape, but an output schema exists to carry that.

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?

Three tight sentences: formula and legal basis first, then parameter semantics, then the risk warning. No filler, and the most decision-relevant point (rate varies by base tax) is placed last for emphasis rather than buried.

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?

With an output schema present and annotations covering the safety profile, the description only needs to nail inputs and caveats, which it does for all four parameters. The remaining gap is that it warns rates differ per base tax without indicating the actual per-tax rates, so an agent still cannot resolve the right rate on its own.

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 0% (titles only), so the description must compensate and largely does: it documents all four parameters with units, types, defaults and bounds. The main gap is that rounding only says 'default DOWN' without listing the accepted values (UP/HALF_UP/etc.), leaving an enum-like choice undocumented.

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 (한국 지방교육세를 ... 계산한다) plus the exact formula (본세 x 부가세율) and the statutory basis (지방세법 제151조). The resource is distinct from siblings such as tax.kr_registration_license_tax or realestate.kr_local_property, so the agent can pick it out without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The closing sentence gives real usage caution — do not blindly use the default rate because each base tax carries a different rate — which is decent context. However, it never names an alternative tool or states when to prefer a sibling (e.g. a full local-tax calculator vs. this add-on step), so tool-selection guidance remains implied rather than explicit.

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