Skip to main content
Glama
UpstageAI

korean-tax-mcp

by UpstageAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

casebook_search

Read-onlyIdempotent

Search the NTS 2025 Tax Interpretation Casebook of 96 curated Korean tax cases by issue or keyword to find document number, reply date, field, issue, and answer summary.

Instructions

Search the NTS 2025 Tax Interpretation Casebook (96 curated cases). 국세청 「2025 세법해석 사례집」 쟁점 검색. 언제: 국세청이 대표 사례로 고른 해석을 빠르게 볼 때(오프라인, 즉시). 최신·전체 해석은 search_tax_rulings. 반환: {결과: [{문서번호, 회신일, 분야, 쟁점, 답변요지, 쪽, 점수, 인용}]}. 읽기 전용, 외부 호출 없음.

Input Schema

NameRequiredDescriptionDefault
kNo결과 수 1~10
areaNo분야 필터 (선택)
langNoOutput language. 'en': English keys and labels, official English texts where available (tax treaties, statutes), other Korean texts returned with a host_ai_translate instruction (your AI translates); Solar machine translation only when UPSTAGE_API_KEY or on-prem Solar is configured. 기본 'ko'ko
queryYes쟁점 문장이나 키워드

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.1
    • changedInput schema / properties / lang / description
      Previous value: -"Output language. 'en': English keys and labels, official English texts where available (tax treaties, statutes), titles/summaries machine-translated by Upstage Solar when UPSTAGE_API_KEY is set. 기본 'ko'"New value: +"Output language. 'en': English keys and labels, official English texts where available (tax treaties, statutes), other Korean texts returned with a host_ai_translate instruction (your AI translates); Solar machine translation only when UPSTAGE_API_KEY or on-prem Solar is configured. 기본 'ko'"
  2. Changed7 schema fields changedv0.4.0
    • changedInput schema / properties / area / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "법인",
+      "부가",
+      "소득",
+      "상증",
+      "양도",
+      "국기",
+      "국조",
+      "종부"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / area / description
      Added value: +"분야 필터 (선택)"
    • addedInput schema / properties / k / description
      Added value: +"결과 수 1~10"
    • addedInput schema / properties / k / maximum
      Added value: +10
    • addedInput schema / properties / k / minimum
      Added value: +1
    • addedInput schema / properties / lang
      Added value: +{
+  "default": "ko",
+  "description": "Output language. 'en': English keys and labels, official English texts where available (tax treaties, statutes), titles/summaries machine-translated by Upstage Solar when UPSTAGE_API_KEY is set. 기본 'ko'",
+  "enum": [
+    "ko",
+    "en"
+  ],
+  "title": "Lang",
+  "type": "string"
+}
    • addedInput schema / properties / query / description
      Added value: +"쟁점 문장이나 키워드"
  3. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so '읽기 전용, 외부 호출 없음' largely repeats structured data. However, the description adds genuinely new behavioral context: the tool works offline and returns instantly, and it enumerates the returned record fields — valuable since no output schema exists.

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?

Front-loaded with the purpose, then cleanly split into '언제' (when) and '반환' (returns) blocks that an agent can scan quickly. The only waste is the purpose sentence being stated twice, once in English and once in Korean, which is mild redundancy rather than bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by enumerating the return fields, and it covers scope, selection criteria, an alternative tool, and the offline/instant behavior. Nothing an agent needs in order to call this correctly is 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 description coverage is 100%, so k, area, and lang are already documented in the schema, including the enum values. The description adds no syntax, formatting, or query-construction guidance beyond what the schema provides, so the baseline of 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?

States a specific verb and resource ('Search the NTS 2025 Tax Interpretation Casebook') and scopes it precisely with corpus size (96 curated cases) and vintage (2025). It also explicitly distinguishes itself from the sibling search_tax_rulings, so an agent can choose without opening either schema.

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

Usage Guidelines5/5

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

The '언제' block gives an explicit when-to-use condition (quickly viewing interpretations the NTS selected as representative, offline/instant) and names the alternative for the contrasting case ('최신·전체 해석은 search_tax_rulings'). Both the selection condition and the exclusion are stated.

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